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
Enum values supplied via input variables or returned in responses are not correctly applying the coercion rules defined by the GraphQL spec. This was previously raised by issue #262, however that issue was incorrectly closed.
Result Coercion
GraphQL servers must return one of the defined set of possible values. If a reasonable coercion is not possible they must raise a field error.
Input Coercion
GraphQL has a constant literal to represent enum input values. GraphQL string literals must not be accepted as an enum input and instead raise a query error.
Enum values supplied via input variables or returned in responses are not correctly applying the coercion rules defined by the GraphQL spec. This was previously raised by issue #262, however that issue was incorrectly closed.
https://graphql.github.io/graphql-spec/June2018/#sec-Enums
https://graphql.github.io/graphql-spec/June2018/#sec-Coercing-Variable-Values
https://graphql.github.io/graphql-spec/June2018/#sec-Value-Completion
The behaviour as currently implemented:
Invalid enum value declared within query string: ✅ PASS
Query:
Result:
Invalid enum value declared within input variables: ❌ FAIL
Query:
Variables:
{"episode": "FINAL_FRONTIER"}
Result:
Expected:
Invalid enum value returned by a resolver: ❌ FAIL
Query:
Result:
Expected:
The text was updated successfully, but these errors were encountered: