Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 25, 2026

Annotates 10 classes in graphql.language package with JSpecify nullability annotations and removes them from the exemption list.

Annotated Classes

  • DirectiveLocation, DirectivesContainer (interface), Document
  • EnumTypeDefinition, EnumTypeExtensionDefinition, EnumValueDefinition
  • Field, FieldDefinition, FragmentDefinition, FragmentSpread

Approach

Field nullability: Core fields (name, type, typeCondition) are marked @Nullable to allow test code to create incomplete instances for validation testing.

Getter enforcement: Getters use assertNotNull() to satisfy NamedNode contract and fail fast:

private final @Nullable String name;

@Override
public String getName() {
    return assertNotNull(name, () -> "name cannot be null");
}

Builder leniency: Builders accept nullable values without validation, supporting existing test patterns that create invalid AST nodes.

List copying: deepCopy() methods use assertNotNull() on list results since AbstractNode's deepCopy(List) returns @Nullable List.

Original prompt

Task

Add JSpecify annotations to the following 10 classes in the graphql.language package, following the established JSpecify annotation pattern documented in .claude/commands/jspecify-annotate.md.

Classes to annotate

  1. graphql.language.DirectiveLocation
  2. graphql.language.DirectivesContainer
  3. graphql.language.Document
  4. graphql.language.EnumTypeDefinition
  5. graphql.language.EnumTypeExtensionDefinition
  6. graphql.language.EnumValueDefinition
  7. graphql.language.Field
  8. graphql.language.FieldDefinition
  9. graphql.language.FragmentDefinition
  10. graphql.language.FragmentSpread

Instructions

Follow the JSpecify annotation process documented in .claude/commands/jspecify-annotate.md:

  1. Set each class to be @NullMarked at the class level
  2. Remove all redundant @NonNull annotations that IntelliJ may have added
  3. Check Javadoc for @param tags mentioning "null", "nullable", "may be null"
  4. Check Javadoc @return tags mentioning "null", "optional", "if available"
  5. Inspect method implementations that return null or check for null
  6. Consider GraphQL specification details when determining nullability
  7. For Builder static classes, label them @NullUnmarked and no further annotations needed

Validation

After making changes, run the NullAway compile check:

./gradlew compileJava

If you find NullAway errors, make the smallest possible change to fix them. You can use assertNotNull with a message if needed.

Cleanup

  1. Remove each completed class from the exemption list in src/test/groovy/graphql/archunit/JSpecifyAnnotationsCheck.groovy
  2. Delete all unused imports from the classes you've annotated
  3. Do not make spacing or formatting changes - only make minimal changes necessary for the annotations

Reference

Look at existing annotated classes like IntValue.java, StringValue.java, AbstractNode.java in the same package for reference patterns.

This pull request was created from Copilot chat.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI changed the title [WIP] Add JSpecify annotations to 10 classes in graphql.language package Add JSpecify annotations to 10 language package classes Jan 25, 2026
Copilot AI requested a review from dondonz January 25, 2026 07:00
@dondonz dondonz changed the base branch from copilot/add-jspecify-annotations-to-classes to master February 8, 2026 07:16
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

Successfully merging this pull request may close these issues.

2 participants