Could please add JsonAnyGetter and JsonAnySetter annotations support? about jackson-dataformats-text HOT 3 OPEN

Ok, at high level I think this makes sense, and I thought there was an issue for it, but apparently not.
It is something I have thought a bit about, although without coming to a conclusion.

Challenge here is that any-properties are really handled at databind level, without any knowledge of underlying format. So as-is, there is no way to really customize this for CSV use case.
This means that:

1. It is possible to read/write any properties for cases where POJO has fewer entries than CSV schema -- but names have to map
2. There is no way to handle truly unknown columns.

So question would be that of how to map such extra data. Answer may have to vary between serialization, deserialization.

For deserialization one would either have to use synthetic names ("1", "2", templating, something), and that might work quite easily. Use of Collection would seem to make sense, but in practice could only support Collection<String>; and would be incompatible with existing logic of calling method once per extra property.

For serialization things might be easier, come to think of that... if there was a way to indicate special arrangement. Perhaps Jackson 3.0 could have capability introspection which would indicate alternate call for such extra data, for formats that do not have true name/value pairing at low level (CSV is positional and name binding is extra layer).

from jackson-dataformats-text.

Isn't this already supported? https://github.com/FasterXML/jackson-dataformat-csv/blob/master/src/test/java/com/fasterxml/jackson/dataformat/csv/deser/AnySetterTest.java

from jackson-dataformats-text.

@amr Good point -- so it'd be due to issue 109 (from old repository) having been implemented.

from jackson-dataformats-text.