-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Fix typing for isNonNullType
#3597
Conversation
= If a type is a non-null type, then the wrapped type must be nullable. = Introduces `GraphQLNullableInputType` and `GraphQLNullableOutputType` to properly represent the result when `isNonNullType` is called on parameters of type `GraphQLInputType` or `GraphQLOutputType`.
👷 Deploy request for compassionate-pike-271cb3 pending review.Visit the deploys page to approve it
|
Hi @yaacovCR, I'm @github-actions bot happy to help you with this PR 👋 Supported commandsPlease post this commands in separate comments and only one per comment:
|
isNonNullType
isNonNullType
isNonNullType
isNonNullType
My guess is that this qualifies as a "bug fix" and can go into a patch release. |
Motivation: 1. Makes it easier to understand the type hierarchy. 2. Adding a new type, were it ever to happen, would require fewer code changes. Depends on graphql#3597
Yes, but the patch releases don't make sense in alpha :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My guess is that this qualifies as a "bug fix" and can go into a patch release.
Motivation: 1. Makes it easier to understand the type hierarchy. 2. Adding a new type, were it ever to happen, would require fewer code changes. Depends on graphql#3597
Motivation: 1. Makes it easier to understand the type hierarchy. 2. Adding a new type, were it ever to happen, would require fewer code changes. Depends on #3597
GraphQLNonNull wrapper can only be applies to nullable types related: graphql#3597 see also: graphql#3617 (comment)
GraphQLNonNull wrapper can only be applies to nullable types related: graphql#3597 see also: graphql#3617 (comment)
`GraphQLNonNull<GraphQLNullableType>` This is related to graphql#3597, in the sense that graphql#3597 made the `GraphQLNonNull<GraphQL*Type>` => `GraphQLNonNull<GraphQLNullable*Type>` change in other code points related to the `isNonNullType` function, but not within `GraphQLWrappingType` or assertNonNullType. This PR was prompted by the uncovering of a bug by a different PR, see: graphql#3617 (comment)
`GraphQLNonNull<GraphQLNullableType>` This is related to graphql#3597, in the sense that graphql#3597 made the `GraphQLNonNull<GraphQL*Type>` => `GraphQLNonNull<GraphQLNullable*Type>` change in other code points related to the `isNonNullType` function, but not within `GraphQLWrappingType` or assertNonNullType. This PR was prompted by the uncovering of a bug by a different PR, see: graphql#3617 (comment)
) `GraphQLNonNull<GraphQLNullableType>` This is related to #3597, in the sense that #3597 made the `GraphQLNonNull<GraphQL*Type>` => `GraphQLNonNull<GraphQLNullable*Type>` change in other code points related to the `isNonNullType` function, but not within `GraphQLWrappingType` or assertNonNullType. This PR was prompted by the uncovering of a bug by a different PR, see: #3617 (comment)
= If a type is a non-null type, then the wrapped type must be nullable.
= Introduces
GraphQLNullableInputType
andGraphQLNullableOutputType
to properly represent the result whenisNonNullType
is called on parameters of typeGraphQLInputType
orGraphQLOutputType
.