Skip to content
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Merge branch 'master' into copilot/add-jspecify-annotations-9b68a1b9-…
…5125-48d5-add7-382dfedc3cc7
  • Loading branch information
dondonz committed Feb 20, 2026
commit a18d5ee5dc44cbe588d70d3b0344678d6535e24d
3 changes: 0 additions & 3 deletions .claude/commands/jspecify-annotate.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,6 @@ Analyze this Java class and add JSpecify annotations based on:
5. Method implementations that return null or check for null
6. GraphQL specification details (see details below)

IntelliJ's infer nullity code analysis isn't comprehensive so feel free to make corrections.

## Pattern Examples

Here are concrete examples of common annotation patterns:
Expand Down Expand Up @@ -125,4 +123,3 @@ The bound on a type parameter determines whether nullable type arguments are all
- When the type parameter represents a concrete non-null object
- Even if some methods return `@Nullable T` (meaning "can be null even if T is non-null")
- Example: `Edge<T>` with `@Nullable T getNode()` — node may be null, but T represents the object type

Loading
You are viewing a condensed version of this merge commit. You can view the full changes here.