Encode query params when navigation is triggered in useURLState #4288
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

We currently have a bug where special characters get lost (replaced by an empty space) in the query browser, only after using the
GroupandSortactions. See #4158.This is happening because (when a navigation is triggered using the
useURLStatehook) the query expression param is not being encoded before being sent back to the URL. This PR fixes that and also for additional cases that were not listed in the original issue i.e. when comparing two profiles and closing one of the compared profiles.How to reproduce:
Add the following to your
parca.yamlfile to add the label valueUsing the query browser, query for the label value above (querier.+) and then try to sort or group, and you should get the error below, and notice in the query browser that the plus sign has been replaced by an empty space.
Resolves #4158