<@U0C1NM397>: not sure if there is a good way to ...
# jackson-kotlin
a
@mbickel: not sure if there is a good way to have it ignore the primary constructor and use a default one, I think that is what you are wanting to do. I’d have to research it more. I think the issue is that integration points with Jackson for the module are limited in terms of controlling its decisions. Not sure if you can do JsonCreator on the default constructor (how in Kotlin to target the invisible constructor created when you have all default values available), and have it also use the setters at the same time.