-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
4.2 M2
I have 2 missing configuration parameters.
ConfigManager and ConfigManager2018 do not log the same warnings
Warnings of ConfigManager :
- The parameter 'workspaces.profile.list' is not valued. Configuration is not initialized.
- The parameter 'workspaces.member.added.send.notification' is not valued. Configuration is not initialized.
Warnings of ConfigManager2018 (only one instead of 2 and with a untranslated key)
- The parameter 'workspaces.member.added.send.notification' is not valid with value 'null' :
- plugin.core-ui:PLUGINS_CORE_UI_DEFAULT_VALIDATOR_MANDATORY
- Est référencé par
-
RUNTIME-2851 Let Configuration parameters decide how to save themselves via their ElementType
-
- Open
-
ConfigManager2018 considers the configuration is incomplete only if mandatory parameters are empty.
It should consider the configuration is incomplete as soon as a configuration parameter is NOT valued (mandatory or not!)
Pb: definitionAndValues does not allow to see the difference between an unvalued parameter and an empty parameter