You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
You could go back to see which PR introduced the issue. I suspect that is was a "refactor" PR that just made a minor dependency upgrade, but somehow is causing issues.
Unfortunately we do not have UI tests in dashboard to detect these issues before merging, and this is not the first time something like this happens. A few UI tests would be a big help in that regard.
In case of #2006 it started with version 3.3.0. Could you try to find out the earliest release that introduced the issue, so we can narrow down which commit introduced the issue.
@visualfanatic since you have more insight into #1948, could you take a quick look at this issue here? it may be related to the React context API change, there are also a few similar new issues where an action in the UI has no effect, so I would assume it may be a context issue, which is one of the major changes in #1948.
Activity
parse-github-assistant commentedon Jan 12, 2022
Thanks for opening this issue!
mtrezza commentedon Jan 12, 2022
I was able to reproduce this issue in 4.0.0-beta.1 and 4.0.0-alpha.5.
404-html commentedon Jan 15, 2022
This looks like a general problem with reading query string params as opening parse dashboard URL that contains filtering have no effect.
mtrezza commentedon Jan 15, 2022
You could go back to see which PR introduced the issue. I suspect that is was a "refactor" PR that just made a minor dependency upgrade, but somehow is causing issues.
Unfortunately we do not have UI tests in dashboard to detect these issues before merging, and this is not the first time something like this happens. A few UI tests would be a big help in that regard.
404-html commentedon Jan 15, 2022
Git bisect pointed following commit: 1ff1057
[-]Applying filers not working[/-][+]Applying filers not working #easymoney[/+][-]Applying filers not working #easymoney[/-][+]Applying filers not working[/+]mtrezza commentedon Jan 21, 2022
@404-html There are a couple of similar looking issues where something in the UI is not working / has no effect:
In case of #2006 it started with version 3.3.0. Could you try to find out the earliest release that introduced the issue, so we can narrow down which commit introduced the issue.
404-html commentedon Jan 21, 2022
Hey @mtrezza, in my previous comment I pointed exact commit which introduced the issue.
mtrezza commentedon Jan 22, 2022
@visualfanatic since you have more insight into #1948, could you take a quick look at this issue here? it may be related to the React context API change, there are also a few similar new issues where an action in the UI has no effect, so I would assume it may be a
contextissue, which is one of the major changes in #1948.damianstasik commentedon Jan 22, 2022
@mtrezza There were some regressions caused by two of my recent refactors and I created a PR with fixes for the issues you mentioned.
[-]Applying filers not working[/-][+]Applying filters not working[/+]mtrezza commentedon Jan 23, 2022
Thanks @visualfanatic for the quick fix! I can confirm it fixes all 3 issues and I already merged the PR, released as
4.0.0-alpha-11.