ljacqu
ljacqu
In AuthMe, we handle invalid YAML differently and have to override the YamlFileResource for that reason. Goal within this issue is to introduce more exception types that extend from ConfigMeException...
It might be interesting to replace SnakeYAML with SnakeYAML engine, which explicitly does not support beans: https://bitbucket.org/snakeyaml/snakeyaml-engine/src/master/ This is fine for our use case, since we dissect beans before exporting...
The inline array properties have a separator so that multiple elements can be stored as a simple text, but what if one of those elements needs to have the separator...
The classes extending `Property` should be organized in more packages.
Create a helper task that scans an existing YML file and creates Property declarations based on it.
As seen in AuthMe, sometimes users need to report their configuration files but such files might include sensitive information like passwords we want to make sure users don't expose. Potentially...
The bean mapper is quite complicated and it would be pretty neat if we could have a way to log some of the stuff that's happening. Ideally this would happen...
For more complex beans it is interesting to allow users to define that a String/collection/map is empty that it should not be exported. Thinking of something similar to Jackson's `@JsonInclude(NON_EMPTY)`.
Relates to #128 (which is about PropertyBuilder method names) PropertyInitializer should offer more methods for list and set properties, and maybe other things too. Can be potentially moved into 1.4...
For #214 it was necessary to introduce a configuration to not split dots in paths. I think the feature should be removed altogether for ConfigMe 2.0 because I can't really...