-
Notifications
You must be signed in to change notification settings - Fork 2k
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
GraphQL validators fail on situation which can never happen #2189
Comments
@mrtnzlml This expected behavior. According to the specification, the algorithm doesn't take
In general, GraphQL validation doesn't take to account runtime values of query variables. However, we need to consider the complexity and runtime cost of such deep analyzes. But in any case, we can't change validation algorithm without change to GraphQL specification so if you still think it's important for GraphQL to handle this use case please open an issue here: https://github.com/graphql/graphql-spec |
Hi! So I am actually not sure if this is a bug or not. But seems logical to me. I have the following query:
(you can try it here)
As you can see, this query will either return variant A or variant B so always only one ID. However, GraphQL compains with the following error:
But this situation will never happen. Is it maybe a bug in some validator?
The text was updated successfully, but these errors were encountered: