Fix auto filtering issue with collection operators #2531
Merged
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.
🔗 Issue Links
Provide all Jira tickets and/or Github issues related to this PR, if applicable.
🎯 Goal
Fix an issue when using auto-filtering with collection operators where the array of values, contains items of types that are not directly comparably for CoreData.
📝 Summary
The crash is caused because the values array contains items of type ChannelType which is not directly comparable for CoreData.
🛠 Implementation
We are using the same approach we used to resolve the problem with the FilterKey value. We are using the valueMapper provided by the FilterKey to map the values into a CoreData comparable format.
☑️ Contributor Checklist
🎁 Meme
Provide a funny gif or image that relates to your work on this pull request. (Optional)