Set of custom objects with `IGNORE_UNKNOWN` brokes silently csv about jackson-dataformats-text HOT 3 CLOSED

Thank you for reporting this. Broken output is wrong, regardless, so I hope this is something that can just be fixed. I am not against option(s) that allow choosing simple toString() to be used, if a good API approach can be found (that is, simple, consistent with existing config options, intuitive).

from jackson-dataformats-text.

Ok. So the technical challenge is that END_OBJECT for nested object is assumed to be the end of outermost object, which should trigger end-of-line. In this case this is false assumption, due to nesting.
I will have to think about how to handle this more reliably, first, to get rid of the false linefeed.

Second problem, then, is whether there might be better handling here for nested POJOs: as things are, arrays can be handled by using array separator. But it is not clear what should be done for contents.
I think use of @JsonValue for Person might work here, I'll check that to make sure.

from jackson-dataformats-text.

Yes; use of @JsonValue does work, for serialization, and in this particular case actually even prevents the linefeed (because no START_OBJECT/END_OBJECT writes are done, given that value becomes just a String).

@pimuzzo You may see if @JsonValue on Person might work for you. I will try to resolve the output problem wrt linefeed.

from jackson-dataformats-text.