The no-args constructor is not necessary for all serializarers and deserializers. For example. when using Micronaut with serde, it's perfectibily acceptable to not have the no-args constructor for serialization and deserialization to be successful. Not only that, but it actually interferes with the deserialization process when the includeSetters option is set to false (all properties constructor would require being annotated with @JsonCreator for all properties to be set accordingly).
As such, I'm creating this PR which implements the includeNoArgsConstructor option, set to true by default for backwards compatibility reasons and allows the user to disable the generation of the no-args constructor.
Edit: second commit reverts default compiler version for integration-tests to 1.6 because I had change it to 1.8 to run the tests locally and accidentally committed it
Motivation
The no-args constructor is not necessary for all serializarers and deserializers. For example. when using Micronaut with serde, it's perfectibily acceptable to not have the no-args constructor for serialization and deserialization to be successful. Not only that, but it actually interferes with the deserialization process when the
includeSettersoption is set to false (all properties constructor would require being annotated with@JsonCreatorfor all properties to be set accordingly).Example showcasing motivation: micronaut-serde-examples.
Purposal
As such, I'm creating this PR which implements the
includeNoArgsConstructoroption, set to true by default for backwards compatibility reasons and allows the user to disable the generation of the no-args constructor.Edit: second commit reverts default compiler version for integration-tests to
1.6because I had change it to1.8to run the tests locally and accidentally committed it