-
Improvement
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Saigon 15, Basel 50, Basel 52
-
13
Currently, if a yaml file is loaded with a property that doesn't exist in the corresponding class, we simply log the problem and continue. Ideally, we'd like to keep track of those problems to be able to report them in the config app. They should not necessarily prevent the file from being loaded, but it is likely a user error, such as a typo, that leads to this, so users should be warned.
Just logging it seems weak, considering that we have better error handling capabilities in the new config api and app. The current log is particularly weak, since it can't report where the unknown property comes from (what file, for which definition, which registry, etc)
+ we could perhaps do the same thing in node2bean.
- is depended upon by
-
CFGUI-11 Improve display of warnings and errors
- Closed
- is related to
-
MAGNOLIA-6324 Multifield sub-field requires extra name property when configured from YAML
- Closed
- relates to
-
MAGNOLIA-6736 Expose Map2Bean conversion errors via DefinitionProvider interface
- Closed
-
MAGNOLIA-6743 Aggregate problems during Node2Bean conversion
- Closed
- mentioned in
-
Page Loading...