There are various lazy-initialized fields with nullability workarounds in accessor methods which historically got addressed through suppressing the warnings. This even carried over to our use of JSpecify in Spring Framework 7.0.
Let's finally clean this up through corresponding revisions of the code flow so that field nullability is handled explicitly, even at the expense of changing the nullability signature of a couple of accessor methods.
There are various lazy-initialized fields with nullability workarounds in accessor methods which historically got addressed through suppressing the warnings. This even carried over to our use of JSpecify in Spring Framework 7.0.
Let's finally clean this up through corresponding revisions of the code flow so that field nullability is handled explicitly, even at the expense of changing the nullability signature of a couple of accessor methods.