Steps to reproduce:
- Go to an invalid search url, e.g. http://localhost:5173/search/invaliduser
- Search for an existing user in the top search box
- A client side redirect is triggered but the error doesn't get cleared, nor does the new user get loaded (the getUser RF query isn't run). Refreshing the page will load the new user correctly.
Expected behavior:
- The error should be cleared when a new search is made
- The new user should be loaded and displayed without needing to refresh the page
Additional context:
If you search for a user that exists, and then another one that exists, it works as expected.