Closed scprek closed 2 months ago
This is bug in micronaut-serilization, generted code is fine
Or, maybe I'm wrong. Is it work with jackson?
I guess normally with Jackson and enum classes, I don't make a custom method and annotate as json creator. By default it just works? And then when you set those properties on the mapper it automatically handles all the cases
I tried a few kotlin generators all with Jackson and they all did the unannotated companion object encode/decode. Not sure why even the spring one has it
Yes, I was wrong. Even in the templates there was a mention of the useEnumCaseInsensitive
setting, it was just impossible to set it via the plugin. Also, I improved the templates a little bit so that the generated code was perfect.
So when a new option is added here does it always require a change to the gradle plugin too? Like https://github.com/micronaut-projects/micronaut-gradle-plugin/commit/83dd0697500ea970ae3a2aaba6cdddedf9f22c73 to add the interface option.
Or is there some dynamic way the plugin can handle new options added?
Just curious
Yes, I agree, it is inconvenient. I don't know why it was done this way, I just added new properties. I myself thought that it would be necessary to add some block with dynamic properties, so as not to depend on the plugin.
Expected Behavior
Allow these application configuration settings to work and accept case insensitive enums
Upstream Example
Actual Behaviour
Steps To Reproduce
Environment Information
Example Application
No response
Version
4.5.1