Eugene Lukash

Ok, since Jackson implementation is there, are there any volunteers to go low-technology approach of copy-paste-edit-add-some-if-else etc to provide the support for Jsonb? will review and accept PR. Frankly, some...

@bmhm thank you for tracking/continuing to moving this forward! I have a side note, so as a part of our experiments (latest released only as `2.8.0-dt-experimental-7`) we have metamodel generator...

Thank you for reporting this. Sorry for late response. Need more context on this, if we introduce such an option, then, is `@JsonAutoDetect` harmful or inadequate in any particular way,...

Just changed to `JsonIgnore` on fields which we've already used in some other places, so `JsonAutoDetect` no longer generated, released in 2.11.0

Thank you for bringing this out. This might look as something at least partially addressed by `immutableCopyOf` routines, first introduced in https://github.com/immutables/immutables/issues/325 . Since then, we've added some support for...

if we do the same as in #171 , a system property, would it work? I'll look into maybe annotation processor options too, IIRC system properties can be accessed from...

Thank you for the feature request! Need to understand the gap: what has to be done for this to work? Currently, we have a number of knobs, and, basically, in...

`fallbackNullableAnnotation` gets many occurences work, but the difference is that JSpecify's nullable is exclusively `TYPE_USE` and we don't apply those in all places, or apply in some cases incorrectly

Current master has improved(fixed) support for type-use annotations, and in particular, `@NullMarked` should work on a type or (parent) package, and JSpecify's `Nullable` propagates to relevant parameters/fields generated code

2.11.0 just released on central