Repository navigation
fix: Resolve expressions set before first render - #90
Merged
Merged
Conversation
Sorting and filtering expressions assigned before the first update were stored without resolving them against the column configuration. Framework wrappers hit this on every initial binding. Sort expressions ignored the column comparer and case sensitivity, and kept 'none' as a sort. Filter expressions set after columns kept string conditions and were never applied. Both now resolve on assignment and again on column configuration. Closes #86
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sorting and filtering expressions assigned before the first update were stored without resolving them against the column configuration. Framework wrappers hit this on every initial binding.
Sort expressions ignored the column comparer and case sensitivity, and kept 'none' as a sort. Filter expressions set after columns kept string conditions and were never applied.
Both now resolve on assignment and again on column configuration.
Closes #86