Jonas Konrad

#1853

@denizhusaj #3416 (which fixed the CVE #2816) specifically fixed the StackOverflowError that can be caused by deeply nested JSON. This is not an issue for JsonNode anymore because in 2.13.0...

@denizhusaj i cannot reproduce that issue. I tried a nested JsonNode object with 50000 levels like in your example. It parsed just fine. Maybe your error comes from JsonNode.toString? That...

I can't say that, it's tatu's decision. However I'm not convinced a depth limit would help with "long texts take a long time to parse" completely. In general you can...

jackson is not responsible for syntax highlighting of output.

At the moment, jackson-databind has no machinery to pass on format-specific information like this. Also see #36 for yaml, and #254 for toml.

i dont understand the issue, can you give a test case? Also without micronaut please, since we introduce our own modifications to bean scanning in micronaut.

@liang-shen i can understand your description, but please give an example where this is actually problematic.

Yes this is also the behavior for other annotations, the best example being `@JsonProperty`: ```java class Test { private String foo; @JsonProperty("bar") public String getFoo() { return foo; } public...

have you tried the coercion config?