Closed AdamTorma closed 4 years ago
It seems like the bug is in Apollo / graphql-tools, not in graphql-iso-date, so this issue can be closed!
It looks like I was able to resolve this by making sure the names match what is defined in the graphql-iso-date Scalar files:
resolvers:
DateTime: GraphQLDateTime
Date: GraphQLDate
Time: GraphQLTime
schema:
scalar DateTime
scalar Date
scalar Time
In my resolvers, I use something like:
(example taken from the Apollo Docs)
Unfortunately, adding these internal values results in an error:
Everything works fine when using "regular" enums without internal values. On the other hand, the code above works as intended when graphql-iso-date isn't used.
I made this codesandbox, just uncomment the section with the enum resolver to see the problem in action.
Any ideas how to fix this issue?