Currently, if you want to use another naming scheme in config files than in the java source code, you need to specify and separately update an @SerialzedName annotation. In order to fix this, I suggest a naming scheme annotation which allows to specify a serialized naming scheme for the given config value, section, or config.
It should work similar to #4 's NameConvention annotation, however SerializedNameConvention is a better match imo
Ideally, it accepts a NamingScheme enum value, or a custom class, which implements the NamingScheme interface
Currently, if you want to use another naming scheme in config files than in the java source code, you need to specify and separately update an
@SerialzedNameannotation. In order to fix this, I suggest a naming scheme annotation which allows to specify a serialized naming scheme for the given config value, section, or config.It should work similar to #4 's
NameConventionannotation, howeverSerializedNameConventionis a better match imo Ideally, it accepts a NamingScheme enumvalue, or acustomclass, which implements theNamingSchemeinterface