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 so that specific cases like the one described before can be caught by callers.
See if there are other situations where it would be interesting to have a dedicated exception type
NB: Throwing IllegalArgumentException and IllegalStateException is fine for errors the developer makes while integrating ConfigMe (e.g. invalid property path). Same for "should never happen" kind of deals
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 so that specific cases like the one described before can be caught by callers.
YamlFileResourceProvider)[https://github.com/AuthMe/AuthMeReloaded/blob/master/src/main/java/fr/xephi/authme/service/yaml/YamlFileResourceProvider.java])NB: Throwing IllegalArgumentException and IllegalStateException is fine for errors the developer makes while integrating ConfigMe (e.g. invalid property path). Same for "should never happen" kind of deals