Specify nullness for nodes in the graphql.language
package
#3899
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.
Related: #3878
I applied
@NullMarked
and@Nullable
annotations to these classes:graphql.language.Node
- partially annotated with@Nullable
graphql.language.AbstractNode
graphql.language.ArrayValue
graphql.language.BooleanValue
graphql.language.EnumValue
graphql.language.FloatValue
graphql.language.IntValue
graphql.language.NullValue
graphql.language.ObjectValue
graphql.language.ScalarValue
graphql.language.StringValue
- I was not sure about the nullability ofvalue
, for now I marked it@Nullable
.graphql.language.Value
graphql.language.VariableReference
Notes
SourceLocation sourceLocation
- can contain a null value in all placesPotential problems (will be pointed by #3852 )
EnumValue.Builder#build()
can build anEnumValue
object with a nullname
FloatValue.Builder#build()
can build anFloatValue
object with a nullvalue
IntValue.Builder#build()
can build anIntValue
object with a nullvalue
VariableReference.Builder#build()
can build anVariableReference
object with a nullname