Make NP Dereference hint aware of Objects.requireNonNull(). #6195
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.
The first commit is fixing the test framework itself since some tests were using the
assertNotContainsWarnings
wrong.assertContainsWarnings
checks againsttoString()
which is the full error state, including line number and position.assertNotContainsWarnings
is only checkinggetDescription()
, but the doc was copied fromassertContainsWarnings
which means that all tests which actually followed the doc, didn't verify anything.second commit makes the NPECheck hint
Objects.requireNonNull
aware.fixes #6149