-
Notifications
You must be signed in to change notification settings - Fork 44
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
Relationship filtering - schema inconsistencies #444
Labels
Comments
Lezek123
changed the title
Filtering by related entity id - schema incosistencies
Filtering by related entity id - schema inconsistencies
Jul 2, 2021
Lezek123
changed the title
Filtering by related entity id - schema inconsistencies
Relationship filtering - schema inconsistencies
Jul 2, 2021
I've found a similar case on query {
workersConnection(where: { group: { id_eq: "forumWorkingGroup" } }) {
totalCount
}
} it returns an error:
|
Basic filtering is done. Recursive filtering as illustrated in #453 (comment) is not yet implemented. |
This was referenced Dec 10, 2021
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Filtering by related entity id
As pointed out by @jodator, there is an inconsitency between the output schema and what is actually supported when it comes to relationship filtering.
For example, previously queries like:
Were supported (
contentDirectoryWorkingGroup
isID
of the relatedWorkingGroup
entity in this case).Currently they have to be rewritten into:
But the output schema still contains
group_eq
andgroup_in
parameters.Providing any of those currently causes an error:
Filtering depth
Another issue is that the output schema doesn't reflect the relationship filtering depth limit, so queries like:
Seem to be fine accoring to the schema, but result in an error when executed:
The text was updated successfully, but these errors were encountered: