Skip to content
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

Error Messaging on "type of kind OBJECT can not be used as input" #224

Open
B-Reif opened this issue Jun 7, 2018 · 3 comments
Open

Error Messaging on "type of kind OBJECT can not be used as input" #224

B-Reif opened this issue Jun 7, 2018 · 3 comments

Comments

@B-Reif
Copy link

B-Reif commented Jun 7, 2018

I encountered this error while defining my schema, but I didn't have any idea how to fix it. Eventually I found the error message in graphql-go's source and found this was related to my type being non-nullable.

At least a few other people in #122 had the same issue. Some extra messaging about this case might help.

@enjoylife
Copy link

I agree that the wording of the error is confusing when first encountering it.

Is there a sense of how easy it is to update the messaging to encompass the following?

  • naming the object in question
  • stating if/why it needs to be nullable
  • and steps to fix it

@pavelnikolov
Copy link
Member

pavelnikolov commented Jun 20, 2018

A simple reproducible example would be appreciated.

@bsr203
Copy link

bsr203 commented Sep 24, 2018

For future reference. I too spend some time to find the cause, and was the case as in this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants