(note: follow-up to #2291 in which basic example added on README)

So: beyond initial simple Builder usage shown on README it would be nice to have more in-depth usage example(s).
This could be a wiki page on this repo or jackson-docs, or blog post to link to.

For purposes of Hacktoberfest whoever works on this could do PR for change in README to link to whatever resource gets added.

I have a TypeIdResolver implementation which works around generic type erasure to allow marshaling/unmarshaling of a parameterized type. This works fine when the underlying parameterized type maps directly onto a JSON type e.g. java.lang.Double but when it's a type that needs to be converted to a JSON string e.g. java.time.LocalDate then my TypeIdResolver is asked for a type and I can eit

(note: inspired by #439 work)

As things are, KotlinModule has a few configuration options, and at least 4 are boolean-valued (plus #439 would add one more, at least temporarily). Since they have to be passed separately, adding a new option requires more changes than is ideal, and technically also reduces cross-version compatibility (although constructors should not really be called from outsi

From some real-world usage, the fold method on Java client response classes isn't quite as useful as it is with Scala. Lack of named arguments makes it more error-prone, and it's just not very idiomatic. The most common use case seems to be doing one thing on success status codes, and another (single) thing on error status codes, so duplicating the error logic -- even if it's just a function c

Tools like jq are focused predominantly on their use on the command line, but have a lot of limitations (and bugs!) that jslt doesn't. This is a compliment to jslt btw. :)

To properly replace the usage of jq with jslt, we would like to be able to have some more flexibility with the ways of specifying the input parameters as well as the output.

• Specifying JSON input or JSLT transform input

InstantSerializer doesn't respect any of the following standard Jackson configuration settings:

ObjectMapper#setDateFormat
@JsonFormat(pattern) on an Instant
others?

Instead, I have to create and manually override the default InstantSerializer registered by the module.

This isn't well documented and is definitely confusing when using the library.
Can we make InstantSerializer

It would be nice to have a CSV feature similar to JSON feature JsonGenerator.Feature.WRITE_NUMBERS_AS_STRINGS. Enabling of the feature by mapper.enable(JsonGenerator.Feature.WRITE_NUMBERS_AS_STRINGS) doesn't work for CSV.

I want to write an object of this class:

data class TestData(
        val integer: Int,
        val float: Float
}

as
"1","1.234"
not as
1,1.234