[ACS-10083] Filter not behaving correctly in file and site #11237
+155
−29
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rmnvch
requested review from
DenysVuika,
eromano and
popovicsandras
as code owners
AleksanderSklorz
approved these changes
Oct 1, 2025
|
@rmnvch I added this label for you this time but next time please remember to add A/N BDU to ADF PRs: |
@AleksanderSklorz , right, sorry |
no problem |
DenysVuika
approved these changes
Oct 7, 2025
rmnvch
force-pushed
the
ACS-10083-checklist-filter
branch
from
eeabb4b to
16a6342
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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-10083
The problem is that there were a conflict between properties we use as keys in query and in filter service. For query category id is used and for active filters it was columnKey. With that it was impossible to support page reload preserving filter state.
What is the new behaviour?
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: