You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the Servlet spec, getCharacterEncoding() should never return null. Consequently, MockHttpServletResponse.characterEncoding should not be @Nullable.
Similarly, MockHttpServletResponse.reset() should set the characterEncoding to WebUtils.DEFAULT_CHARACTER_ENCODING instead of null.
Ensuring that characterEncoding is never null will also help to simplify the implementation of several methods in MockHttpServletResponse that currently have non-null checks for the characterEncoding.
The text was updated successfully, but these errors were encountered:
sbrannen
changed the title
MockHttpServletResponse.characterEncoding should not be @NullableMockHttpServletResponse.characterEncoding should not be @NullableJul 29, 2021
According to the Servlet spec,
getCharacterEncoding()
should never returnnull
. Consequently,MockHttpServletResponse.characterEncoding
should not be@Nullable
.Similarly,
MockHttpServletResponse.reset()
should set thecharacterEncoding
toWebUtils.DEFAULT_CHARACTER_ENCODING
instead ofnull
.Ensuring that
characterEncoding
is nevernull
will also help to simplify the implementation of several methods inMockHttpServletResponse
that currently have non-null checks for thecharacterEncoding
.The text was updated successfully, but these errors were encountered: