Applying filters not working

[404-html]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.

Issue Description

When filtering the data URL changes but the browser doesn't refresh. It doesn't matter if filters are applied from filters section or context menu.

Steps to reproduce

1. Go to data browser;
2. Click on "Filters";
3. Click on "Apply these filters";

---

1. Go to data browser;
2. Right click on a cell with data;
3. Click on a "Set filter...";
4. Pick any option.

Actual Outcome

URL changes but nothing happens. Filter panel stays open.

Expected Outcome

Data browser should refresh and show filtered data. I believe in first scenario filters panel should also close.

Environment

Dashboard

• Parse Dashboard version: 4.0.0-beta.1
• Browser (Safari, Chrome, Firefox, Edge, etc.): Chrome
• Browser version: 97.0.4692.71

Server

• Parse Server version: any
• Operating system: Linux
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Google Cloud

Database

• System (MongoDB or Postgres): MongoDB
• Database version: latest
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): MongoDB Atlas

Logs

Nothing gets logged in browser' dev tools.

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 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.

[mtrezza]

I was able to reproduce this issue in 4.0.0-beta.1 and 4.0.0-alpha.5.

[404-html]

This looks like a general problem with reading query string params as opening parse dashboard URL that contains filtering have no effect.

[mtrezza]

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]

Git bisect pointed following commit: 1ff1057

[mtrezza]

@404-html There are a couple of similar looking issues where something in the UI is not working / has no effect:

• Switching apps not working #1994
• File upload in dashboard GUI is not working #2006

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]

Hey @mtrezza, in my previous comment I pointed exact commit which introduced the issue.

[mtrezza]

@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.

[damianstasik]

@mtrezza There were some regressions caused by two of my recent refactors and I created a PR with fixes for the issues you mentioned.

[mtrezza]

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.