-
Notifications
You must be signed in to change notification settings - Fork 155
Document child entity filtering #159
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
Conversation
``` | ||
|
||
> Please note that some suffixes are only supported for specific types. For example, `Boolean` only supports `_not`, `_in`, and `_not_in`. | ||
> Please note that some suffixes are only supported for specific types. For example, `Boolean` only supports `_not`, `_in`, and `_not_in`, but `_` is available only for object and interface types. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean that Arrays of Objects aren't supported, for example?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I described here only the output types of GraphQL, both NonNullable
and List
are just modifiers. Maybe it's misleading? On the other hand, if we mention here the List modifier, then the NonNullable modifier is equal from the GraphQL standpoint and worth including as well, but then it becomes too complex.
Not sure, your choice :)
pages/en/developer/graphql-api.mdx
Outdated
} | ||
``` | ||
|
||
#### Example for child entity filtering |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if "nested" entities is easier to understand? Is there a general term for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, nested makes more sense to me as well.
@azf20 I think we can merge it now, no? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
No description provided.