-
Notifications
You must be signed in to change notification settings - Fork 56
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
Expose graphql errors #39
Comments
The only thing |
I found out what the issue was. It's the added |
Got the same error. Very confusing error message. Please add support for |
I'm honestly not a big fan of supporting |
@kbrandwijk JS GraphQL plugin for Webstorm. |
@schickling Supporting multiple extensions would not be confusing to beginners, if all the docs and gettings starteds just use However, for more advanced users integrating this, that have existing files with a different extension, I see no harm in supporting it. Actually, as far as I'm concerned, everything with a |
I was using comments with |
@kbrandwijk .graphqls seems to be the standard for a backend we are using built on EDIT: I am assuming this file extension EDIT 2: @nexxado Were you able to figure out how to import .graphqls files at all? |
I've just been stuck on this error for over an hour. Why do you even care what the file extension is? I'm telling the package my schema is in that file, the extension of that file is not important and should not be validated. |
Hi @jloveric , @TobiasBales , @wingertge , @jsonmaur and @SachaG ! Could you install |
Available in 1.0.0! |
Using this library i got the following error when trying to run an
graphql-express
server:GraphQLError: Syntax Error: Cannot parse the unexpected character "/".
Using a typedefs as a string and using only
graphql-tools
i got the following error:Error: "login" defined in resolvers, but not in schema
Much easier to understand what went wrong.
Is it possible to expose these kinds of errors to the user when using
graphql-import
?The text was updated successfully, but these errors were encountered: