We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
if (Foo.this.bar != null)
In Spring, we have code like:
if (DefaultRestClient.this.initializers != null) { DefaultRestClient.this.initializers.forEach(initializer -> initializer.initialize(request)); }
Which generates the following error:
/Users/sdeleuze/workspace/spring-framework/spring-web/src/main/java/org/springframework/web/client/DefaultRestClient.java:539: error: [NullAway] dereferenced expression DefaultRestClient.this.initializers is @Nullable DefaultRestClient.this.initializers.forEach(initializer -> initializer.initialize(request));
I would expect such construct not triggering an error.
The text was updated successfully, but these errors were encountered:
Foo.this.bar
Thanks for the report! I've put up a PR #937 to fix this case.
Sorry, something went wrong.
Track access paths of the form Foo.this.bar (#937)
5bedf0a
Fixes #936 We add limited tracking of such access paths, to handle null checks on fields from an enclosing class of a nested class.
@SuppressWarnings("NullAway")
msridhar
Successfully merging a pull request may close this issue.
In Spring, we have code like:
Which generates the following error:
I would expect such construct not triggering an error.
The text was updated successfully, but these errors were encountered: