@JsonInclude(JsonInclude.Include.NON_NULL) not honored on JVM records since 2.16

[rrva]

I found a regression in 2.16.1 compared to 2.15.2.

if I create a jvm record class with non null annotations, they are not honored anymore by the object mapper.

for the following class

@JvmRecord
data class AnnotatedRecordClass (
    @JsonInclude(JsonInclude.Include.NON_NULL)
    val omitFieldIfNull: String?,
    val standardField: String?
)

when an object with omitFieldIfNull set to null on this class, it is still included in the json

If I make the class a regular kotlin data class however, the annotation is honored.

If I downgrade jackson to 2.15.2, it works for jvm records again.

So a regression in handling of jsoninclude annotations on jvm records

[JooHyukKim]

If the problem is reproducible in Java, jackson-databind and if only Kotlin, kotlin-module.

I suppose ur suggesting it's kotlin-module's regression?

[JooHyukKim]

Tested below and jackson-databind from 2.15 to 2.17 seems to all work as expected.

record AnnotatedParamRecordClass(
        @JsonInclude(JsonInclude.Include.NON_NULL)
        String omitFieldIfNull,
        String standardField
    ) {
    }

    record AnnotatedGetterRecordClass(
        String omitFieldIfNull,
        String standardField
    ) {
        @JsonInclude(JsonInclude.Include.NON_NULL)
        public String omitFieldIfNull() {
            return omitFieldIfNull;
        }
    }

    private ObjectMapper MAPPER = newJsonMapper();

    @Test
    public void testJsonIncludeOnRecordParam() throws Exception
    {
        // First, test with non-null value
        assertEquals(a2q("{'standardField':'def'}"),
            MAPPER.writeValueAsString(new AnnotatedParamRecordClass(null, "def")));
        // and then with null
        assertEquals(a2q("{'standardField':'def'}"),
            MAPPER.writeValueAsString(new AnnotatedGetterRecordClass(null, "def")));
    }

[JooHyukKim]

I think it "just" worked, with no intentions included.
Because at this point, one might say it's Kotlin's regression but I think otherwise. There is no test around @JvmRecord and also kotlin-module doesn't have explicit jvm target support for JDK17.

[cowtowncoder]

Definitely sounds like Kotlin issue; will transfer.