Mention issue 2348 (assertNotNull) in release notes for 2.10?

[TysonAndre]

603b395 (Fix #2348) is part of the 2.10 release.

Observed: When I open https://github.com/FasterXML/jackson-databind/blob/master/release-notes/VERSION-2.x , I don't see the substring 2348 anywhere.
Expected: The 2.x branch and master branch update the release notes for 2.10(.0). Mention that the helper readValue will start throwing when null is passed instead of a string (it previously returned null).

I notice that readValue will start throwing in 2.10 for code such as the below, if jsonUsers is the value null (not the string "null"). The application in question doesn't expect null as an actual input, but checked for it anyway as a sanity check. I discovered this in an integration test of handling invalid inputs.

• I agree with the fix but want it documented.

// The assertion causing the exception
    public <T> T readValue(String content, TypeReference<T> valueTypeRef)
        throws JsonProcessingException, JsonMappingException
    {
        _assertNotNull("content", content);

            List<User> users = mapper.readValue(jsonUsers, new TypeReference<List<User>>(){});`

java.lang.IllegalArgumentException: argument "content" is null
	at com.fasterxml.jackson.databind.ObjectMapper._assertNotNull(ObjectMapper.java:4413)
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3187)

I didn't see anything else in github issues mentioning this or linking to that issue.

[cowtowncoder]

Thank you for reporting this gap -- I added it in release notes, as well as on 2.10 wiki page (https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.10) -- latter being compiled from former.

[TysonAndre]

Thanks!

[kumarvinod22]

I'm using com.fasterxml.jackson.core:jackson-databind : 2.13.4.2 getting error
java.lang.IllegalArgumentException: argument "content" is null
at com.fasterxml.jackson.databind.ObjectMapper._assertNotNull(ObjectMapper.java:4829)
Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:

[JooHyukKim]

You may check above, @kumarvinod22.
Issue has been closed 👍🏼