feat(build): add optional Error Prone and NullAway checking - #6613
Merged
Big-Iron-Cheems merged 1 commit intoAug 28, 2026
Merged
Conversation
Add opt-in Error Prone analysis with NullAway configured for JSpecify nullability checking across the Meteor client package.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Type of change
Description
Adds opt-in Error Prone and NullAway static analysis with JSpecify support.
The checks are enabled with
-Perrorprone, allowing nullability issues acrossmeteordevelopment.meteorclientto be detected without affecting normal builds.Related issues
N/A
How Has This Been Tested?
./gradlew buildfor a normal build./gradlew build -Perrorpronefor a null-checking buildBoth builds complete successfully.
Checklist: