Quantum64

@dinomite The issue is the `jsonMapper {}` DSL. I get the same error when using it, but not when using the `ObjectMapper().registerKotlinModule()` syntax. Edit: It seems `.registerKotlinModule()` is still needed...

I agree. I've been subtly working around this issue for at least a year and only had the initiative to report it the last time it took me on an...

Also interesting: even with a "real" zero-argument constructor in the bytecode generated with ```kotlin data class Data @JvmOverloads constructor(val flag: Boolean = true) ``` the test still fails.

I guess I should have tested this before reporting, but the exact same test fails in Java. Looks like this has nothing to do with the Kotlin module at all!...

We have come to rely on `NON_DEFAULT` to substantially reduce data storage requirements. One of our use cases involves a User data object with many fields. Realistically, most users only...

@k163377 Do you have a plan for `value class` deserialization support? With the stabilization of more Kotlin standard library components that utilize `value class`es such as `kotlin.time.Duration`, this is becoming...

In my opinion, the problem is Velocity adding additional fields. Velocity reordering the fields does not violate the specification.

Right! We're all trying to decompile cash show...

I'm in exactly the same spot. Just looks like a stream of binary data in Wireshark, so there isn't much hope of blackboxing it.

I mean you can represent binary data as hexadecimal digits. One byte can be represented as two characters from 0 to f. There's no such thing as "hexadecimal data". Typically...