We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The examples http://dev.apollodata.com/tools/graphql-tools/scalars.html#Own-GraphQLScalarType-instance don't seem to work. Am I missing something?
e.g.,
import GraphQLJSON from 'graphql-type-json'; const resolvers = { ExampleCustomType: GraphQLJSON, ...etc }; export default makeExecutableSchema({ typeDefs, resolvers });
My resolver just returns false. I also tried creating my own types with new GraphQLScalarType({}) and got the same.
false
Then I find this with the following example:
Limit: { __description: '...', __parseValue(value) { return value; }, __serialize(value) { return value; }, __parseLiteral(ast) { ... return parsedLimit; }, }
and const resolvers = { ExampleCustomType: Limit, ..etc } works.
const resolvers = { ExampleCustomType: Limit, ..etc }
I feel I must be missing something really obvious here?
The text was updated successfully, but these errors were encountered:
@scf4 I think this was fixed in #203. If you update to 0.8.3 it should work. What version does npm list | grep grapqhl say you're on?
npm list | grep grapqhl
Sorry, something went wrong.
Great! I was on 0.8.1. Thanks.
Ok, glad it works now!
No branches or pull requests
The examples http://dev.apollodata.com/tools/graphql-tools/scalars.html#Own-GraphQLScalarType-instance don't seem to work. Am I missing something?
e.g.,
My resolver just returns
false
. I also tried creating my own types with new GraphQLScalarType({}) and got the same.Then I find this with the following example:
and
const resolvers = { ExampleCustomType: Limit, ..etc }
works.I feel I must be missing something really obvious here?
The text was updated successfully, but these errors were encountered: