feat: Support filtering by poly components #1092
Merged
Conversation
This file contains 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
stephenh
pushed a commit
that referenced
this pull request
May 18, 2024
# [1.166.0](v1.165.2...v1.166.0) (2024-05-18) ### Features * Support filtering by poly components ([#1092](#1092)) ([2f76e62](2f76e62))
|
🎉 This PR is included in version 1.166.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Previously filters on poly fields could not see below the immediate poly id value.
This was because each poly component has fundamentally different types.
This PR adds support by just exposing each poly component as a dedicated key in the filter, i.e.:
Where
Comment.parentis a poly ofAuthor | Book, and previously we could only filter onparent: ...basic condition on the id....