Tatu Saloranta

@navishsharma How would rounding mode be used, actually? Could you give sample code (assuming config option was added) to show intended use for serialization?

If possible, it'd be great to have Java-only reproduction -- if so, could transfer to `jackson-dataformats-text` where this belong (but can't if there's Kotlin dependency).

I was just hoping to confirm whether this is due to Kotlin Value Class specific details (in which case it might not be CSV-specific, fwtw), or not (in which case...

Ok. I am not opposed to actually making this work (i.e. original usage to be supported), but that'd need to come as contribution. As to failing the combination... sounds reasonable...

I think at this point I'd recommend custom serializer. Although if anyone has time and itch, we now have `DateTimeFeature` which would work well for this use, I think.

I'd be fine with `DateTimeFeature` if support were added, since it'd be very easy way to expose it. But I don't think we have time to implement this for 3.0.0...

Probably makes no difference, but there is now 2.20.0 release to try out.

This: ``` Jackson type: [simple type, class com.example.jsontesterbug.MessageWrapper] ``` shows underlying problem: type is resolved as `MessageWrapper` and that's why `@JsonTypeInfo` does not take effect. This is from getting private...

Yes, there are challenges in buffering and `double` vs `BigDecimal` handling. Since Object and Type Id handling (as well as use of `@JsonCreator` sometimes) typically result in need to buffer...

I think FasterXML/jackson-databind#3730 that was just added should help here.