Enum values provided to scalars #834
Assignees
Labels
Comments
goto-bus-stop
added
bug
goto-bus-stop
added a commit
that referenced
this issue
Feb 14, 2024
…m scalars, fixes #834 Validation does not currently accept something like this: ```graphql scalar Currency type Query { convertToUSD(amount: Int!, currency: Currency!): Int! } query { convertToUSD(amount: 100, currency: EUR) } ``` which is accepted by graphql-js and (rarely) used by customers. I don't love it, but we already accept enum values nested inside lists or objects as input for custom scalars, so it makes sense to accept this too.
goto-bus-stop
added a commit
that referenced
this issue
Feb 14, 2024
…m scalars, fixes #834 (#835) Validation does not currently accept something like this: ```graphql scalar Currency type Query { convertToUSD(amount: Int!, currency: Currency!): Int! } query { convertToUSD(amount: 100, currency: EUR) } ``` which is accepted by graphql-js and (rarely) used by customers. I don't love it, but we already accept enum values nested inside lists or objects as input for custom scalars, so it makes sense to accept this too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Validation does not currently accept something like this:
which is accepted by graphql-js and (rarely) used by customers. I don't love it, but we already accept enum values nested inside lists or objects as input for custom scalars, so it makes sense to accept this too.
The text was updated successfully, but these errors were encountered: