[ACS-8751] Rework search filters to allow initial state and query encoding #10271
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
https://hyland.atlassian.net/browse/ACS-8751
What is the new behaviour?
Query builder service now stores configuration per each configured and used filter including provided values, this configuration is then encoded and pushed to query params, this configuration is updated when any filter is interacted with and when query is executed,
userQuery
is also included. Additionally every filter during initialization now listens topopulateFilters
subject which pushes initial state for the filter when query param is populated and page is reloaded. Additionally when query is executed it updates existing path with new encoded state of filters.Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: