You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue here is path; it's equal to "query TestQuery" and I think it is not exactly compliant with the graphql spec which expects path to be an array of fields. It is an issue for us because we use a federation router in front of the graphql server and path is invalid for the router in this case.
Versions
graphql version: 2.1 rails version: 7.0.7
Expected behavior
Maybe path shouldn't be set when there's a validation error in the query arguments as some other graphql implementations seem to do that.
(It's a separate topic but some implementations accept default values for non-null variables and it's not clear to me what is the right behavior per the spec.)
The text was updated successfully, but these errors were encountered:
Hey, sorry I didn't get back to you on this earlier! I agree that the path on this error should match the spec.
Also, looking back at the spec, I can see that this query doesn't violate it. It's allowed within the given grammar and not expressly prohibited elsewhere.
I'll keep this open until I've checked the paths and removed this error from the project.
Describe the bug
With this query:
This error is returned:
The issue here is
path
; it's equal to "query TestQuery" and I think it is not exactly compliant with the graphql spec which expectspath
to be an array of fields. It is an issue for us because we use a federation router in front of the graphql server andpath
is invalid for the router in this case.Versions
graphql
version: 2.1rails
version: 7.0.7Expected behavior
Maybe
path
shouldn't be set when there's a validation error in the query arguments as some other graphql implementations seem to do that.(It's a separate topic but some implementations accept default values for non-null variables and it's not clear to me what is the right behavior per the spec.)
The text was updated successfully, but these errors were encountered: