Dashboard inaccessible after JS error

[hej2010]

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 a JS error causes the dashboard to crash (white screen), the browser keeps redirecting you to the same page/filter that caused the crash and you have to clear the local storage (the brower_last_location key) to be able to navigate to another page.
Even if you go to the start page or a different class, it still redirects you back.

Steps to reproduce

1. Go to a collection with pointers
2. Set the filter to Unique on a pointer field and apply (same bug as in Crash on filter unique for pointer #2657 )
3. The dashboard gets a JS error TypeError: l.get is not a function and the screen turns white
4. Navigate to a different class
5. You get redirected back to the same page and the JS error causes it to crash again

Deleting browser_last_location in local storage allows you to navigate to a different page.

Actual Outcome

The browser keeps redirecting you to the page that causes the crash.

Expected Outcome

Don't redirect to the previous page on page load.

Environment

Dashboard

• Parse Dashboard version: 7.3.0-alpha.14
• Browser (Safari, Chrome, Firefox, Edge, etc.): Firefox
• Browser version: 140.0.4

Logs

TypeError: l.get is not a function at dashboard.bundle.js:2:2240738

[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]

What's the expected outcome? Where should the browser direct to?

[hej2010]

If I go to a specific URL/class I don't want it to redirect to the last location. Why is the brower_last_location needed?

[mtrezza]

Here is the explanation: #2458