-
Notifications
You must be signed in to change notification settings - Fork 0
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: support relation filter #33
Comments
Not supported for now, but should be added: |
Just exposing foreign key in twentyhq/twenty#2505 for now, and make multiple requests |
Should be possible now that we've moved the findMany endpoint outside of pg_graphql Related: #98 |
@FelixMalfait added the designs to the description |
Behavior updated with CleanShot.2024-10-18.at.18.33.37.mp4 |
@Bonapara actually The feature was about even more advanced filter (person.company.name does not contain X or company.person.address is Y). It's true that for one-to-many relationships we only display it one side of the relation, but I would say this is a specific sub-case for the ID field (from an eng perspective) - and because ID are not user-friendly there's a special UI layer for IDs that retrieve the name/pictures. Let's discuss orally if it's not clear! |
But is filtering on V2 I had in mind (Doable as V1?) CleanShot.2024-10-21.at.10.33.39.mp4 |
Scope & Context
Relation between customs and standards objects has been added recently twentyhq/twenty#2398
Current behavior
We can't make a query filtering on nested relations
Expected behavior
We should be able to make query filtering on nested relations, by example query like that:
Technical inputs
• This ability should be added in the
filter
factories.•
query-builder
should handle them properly based on howpg_graphql
is supposed to receive them.Designs
CleanShot.2024-09-12.at.11.39.09.mp4
The text was updated successfully, but these errors were encountered: