feat: support nullable graphql query #2403
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello, thank you for developing this wonderful library called msw. I am using msw in my graphql project. There I have a Query with nullable return value.
And I generate that type using graphql-codegen.
Here is an example of the generated type.
And I tried to use this query type which may return null in graphql.query and graphql.mutation.
Then I got a type error that nullable queries and mutations are not supported.
I would like to have the actual value returned by a query or mutation set strictly as a type in mock as well.
Therefore, I have modified
GraphQLQuery
to allow null.What do you think?