Skip to content

camelCase properties not mapped at deserialization time #373

Answered by zml2008
Djaytan asked this question in Support
Discussion options

You must be logged in to vote

Ah, that makes sense -- migrating to a discussion because this is not a bug. Configurate's object mapper by default applies normalization to field names, converting camelCase to kebab-case, so the expected field name would be is-ssl-enabled. You can override this for that specific field with the @setting annotation, or change the naming scheme on the object mapper passed to the type serializer collection in the options used by your loader.

Replies: 5 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@Djaytan
Comment options

Answer selected by Djaytan
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #372 on January 21, 2023 01:32.