Allow registering "string-converter hook", for low-level coercion or String mutation #355
Copy link
Copy link
Open
Labels
3.xIssues to be only tackled for Jackson 3.x, not 2.xIssues to be only tackled for Jackson 3.x, not 2.xmost-wantedTag to indicate that there is heavy user +1'ing actionTag to indicate that there is heavy user +1'ing action
Description
Activity
- added3.xIssues to be only tackled for Jackson 3.x, not 2.xIssues to be only tackled for Jackson 3.x, not 2.xand removed
on Aug 30, 2019 Note: created jackson-databind issue too, to increase visibility.
- addedmost-wantedTag to indicate that there is heavy user +1'ing actionTag to indicate that there is heavy user +1'ing action
on Jun 9, 2024
Metadata
Metadata
Assignees
Labels
3.xIssues to be only tackled for Jackson 3.x, not 2.xIssues to be only tackled for Jackson 3.x, not 2.xmost-wantedTag to indicate that there is heavy user +1'ing actionTag to indicate that there is heavy user +1'ing action
One common wish for processing (at various levels) is to be able to modify incoming String values, to either:
12(int)While such functionality is most often needed for formats like
CSVandXML(and perhapsproperties), it seems that due to needed across multiple formats this would really make sense asjackson-corefunctionality.What probably makes sense is to try to figure out abstractions needed, interaction, but require implementations to wire actual activity. In fact, it is almost certainly impossible to do it efficiently and cleanly from within
jackson-coreitself (or from databind).But it should be possible to implement it in core both for API, and wiring for JSON, and then add similar functionality for other textual (and maybe, if there's demand, for binary?) codecs.