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
Hello,
After implementing #7 I realised there is no easy way to define non null fields on GraphQL objects.
E.g. for RelayConnection pageInfo is a Non null field and currently the only way to enforce this would be to create a type mapper to RelayConnection.
The most natural solution is probably another annotation e.g. GraphQLFieldNonNull (To avoid collision with the graphql-core non null).
GraphQLFieldNonNull
There is probably merit in also making any primitives non null by default. (This solves the pageInfo difference from #7 nicely)
Thoughts?
Ciaran
The text was updated successfully, but these errors were encountered:
Correct. Non-Null is something I hadn't gotten around to finishing. Shouldn't be difficult and it'd be nice to fully implement it by:
Sorry, something went wrong.
It seems that the annotation route may not be possible
No branches or pull requests
Hello,
After implementing #7 I realised there is no easy way to define non null fields on GraphQL objects.
E.g. for RelayConnection pageInfo is a Non null field and currently the only way to enforce this would be to create a type mapper to RelayConnection.
The most natural solution is probably another annotation e.g.
GraphQLFieldNonNull
(To avoid collision with the graphql-core non null).There is probably merit in also making any primitives non null by default. (This solves the pageInfo difference from #7 nicely)
Thoughts?
Ciaran
The text was updated successfully, but these errors were encountered: