I can't figure out why the javadocs are saved into the source-tree. I really can't understand why the full record of historic javadocs is stored there. It is about 60x the size of the /src tree!

I presume this is so GH hosts these but isn't there a better way?

$ du -s .[^.]* * | sort -nr
653988	docs
110124	.git
11828	src
164	release-notes
76	.mvn
44	.github
32	attic
``

Jsoniter project (https://github.com/plokhotnyuk/jsoniter-scala) has many impressive performance optimizations; linked f.ex from here:

https://www.reddit.com/r/java/comments/darehu/jackson_release_210/f1ysf1e/

Of ones included, number-parsing would be relevant for this repo.

EDIT: also see (from the comment below)

"Unrelated to jsoniter but this recent port of Lemire's Double parser:

Actual

Using Kotlin 1.4.32 and Jackson 2.13.2.20220324 with jackson-module-kotlin I'm getting an exception

Caused by: java.lang.NoSuchMethodError: 'boolean kotlin.reflect.KClass.isValue()'
	at com.fasterxml.jackson.module.kotlin.KotlinAnnotationIntrospector.findSerializer(KotlinAnnotationIntrospector.kt:88)
	at com.fasterxml.jackson.module.kotlin.KotlinAnnotationIntrospector.findSer

With a file

---
description: 400 - The request was malformed or missing a required field.
content:
  application/json:
    schema: { $ref: '#definitions/BadRequestResponse' }

definitions:
  BadRequestResponse:
    description: Optional information about how the request was bad.
    type: object
    properties:
      fieldName:
        description: >-
          If this error

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