Closed djordjeglbvc closed 4 years ago
Going with simplified config manager design: config manager by itself doesn't care about options and modules, it just reads config data that is provided to it. Modules ask config manager for config options which they need. And that's it.
Tasks 2 and 3 are obsolete, but new task is to modify all configurable modules to pull config data from config manager during initialization.
Summary Currently, configuration manager is just a single list of unorganized configurable options used across the project. Problem is that all options are added manually ad-hoc, without any structure. Goal of this task is a configuration manager organized into separate configuration sections for different modules, registration of arbitrary number of plugin specific configuration options.
Details All modules which currently have some configurable options will be affected by this change (basically most of them), so this task will be split into following subtasks:
Task 2: Move all existing configuration options to their respective modules/pluginsTask 3: Identify new configuration options in modules/plugins, move them to config manager and update modules/plugins to use new config manager api where neededJIRA: AXS-53