Add flag to indicate only @NullMarked code should be checked #1117
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.
Fixes #574
We add a new flag
OnlyNullMarked
to indicate that NullAway can only check code that is@NullMarked
, and hence it is ok to omit the (previously required)AnnotatedPackages
flag. We currently require exactly one of eitherAnnotatedPackages
orOnlyNullMarked
to be passed in; if both flags are omitted or both flags are passed, we fail.As JSpecify and
@NullMarked
become more widely adopted, we may change the policy to allow neither flag to be passed (as NullAway already checks@NullMarked
code out of the box). But for now, we require one of the flags to be passed, to avoid confusion.