Skip to content
New issue

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

Extend null-safety to field level [SPR-15720] #20276

Closed
spring-issuemaster opened this issue Jun 29, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

commented Jun 29, 2017

Juergen Hoeller opened SPR-15720 and commented

After the measures in #20099, we have consistent @Nullable declarations at the method parameter and return type level already. It turns out that @Nullable at the field level is an essential companion, avoiding mismatches between methods and the fields that they access.

Also, Eclipse only supports "full" nullability through annotations: that is, it doesn't differentiate between parameter level and field level. Extending our @NonNullApi / @Nullable semantics to the field level makes it easier to set those up for Eclipse as well.


Affects: 5.0 RC2

Issue Links:

  • #20099 Introduce null-safety of Spring Framework API
  • #20461 ExceptionHandlerMethodResolver loses all handler methods
  • #22124 Exporting a lazily initialized bean (which implements SelfNaming and is annotated with ManagedResource annotation) gives IllegalStateException
  • #20277 org.apache.tomcat.websocket.WsSession.requestUri can be null
  • #20302 JSP tags doesn't pick up JSTL-defined time zone at page level
  • #21087 SpEL : Indexed access within an expression with null variables is no longer a SpelEvaluationException
  • #20311 Revisit nullability annotations towards GA
  • #20215 Backport selected refinements from the nullability efforts in 5.0
  • #20347 Make getters and setters null-safety consistent

Referenced from: commits 46eba3d, 9fc4fb1, 00f4c36, c292a89, 301e2ea, cc74a28, 57f961e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.