Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Allow filtering m2o by CTI subtypes. #1093

Merged
merged 2 commits into from
May 18, 2024
Merged

Conversation

stephenh
Copy link
Collaborator

@stephenh stephenh commented May 18, 2024

Using the same trick/infra as filtering by poly components, we expose the subtypes of pointing-to-CTI m2o fields as sibling suffixes.

I.e. if you have a author.publisher that could be one of two Publisher subtypes, you can now filter to a specific one by doing:

  • em.find(Author, { publisherLargePublisher: { country: "US" } })

Currently this is only implemented for m2os, but we should be able to use the same trick for all relation types.

Using the same trick/infra as filtering by poly components, we expose
the subtypes of pointing-to-CTI m2o fields as sibling suffixes.
@stephenh stephenh merged commit 1a67c5a into main May 18, 2024
5 checks passed
@stephenh stephenh deleted the feat-filter-by-cti-subtypes branch May 18, 2024 13:08
stephenh pushed a commit that referenced this pull request May 18, 2024
# [1.167.0](v1.166.0...v1.167.0) (2024-05-18)

### Features

* Allow filtering m2o by CTI subtypes. ([#1093](#1093)) ([1a67c5a](1a67c5a))
@stephenh
Copy link
Collaborator Author

🎉 This PR is included in version 1.167.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
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant