fix: Filter values are not updating when dependencies are set #23566
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.
SUMMARY
#23400 fixed the following error:
The strategy used for the fix was to store an array of the initial data and always append it when updating the select options. This caused a unintended problem with filter dependencies because the initial data may not be present when the filter values are affected by other filters.
Another problem is that "Dynamically search all filter values" is used when the number of options available exceeds the 1000 threshold and the user needs to search for values that are not loaded on the client side. At this moment, the select is very similar to an async select and the Select All feature will have many challenges as you can see here.
This PR removes the initial data state to fix the dependencies bug and also disables Select All when "Dynamically search all filter values" is checked.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Screen.Recording.2023-04-03.at.14.28.24.mov
Screen.Recording.2023-04-03.at.14.22.15.mov
TESTING INSTRUCTIONS
Check the videos and referenced PRs for instructions.
ADDITIONAL INFORMATION