regression: Old stored query conflicting with new filters applied #35297
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.
Proposed changes (including videos or screenshots)
The problem is: since we store the current query on the local storage, old installations will have some data that's no longer compatible with the new version. For example, fields that have been converted to be an array instead of an string will fail to be processed.
The work to support both, or to make the old compatible with the new is greater than what we get from them (after the first use, the code to support old stored value would become legacy as a new payload will be stored, rendering the code useless from that point). So, quickest solution: change the key where we store, allowing new installations to set new data, and old installations to not fail :)
Issue(s)
Steps to test or reproduce
Further comments
Introduced here: #35147