Currently module configuration is separated into 2 parts. One for the configuration that configures the object and one that contains custom parameters specified by a configuration file.
There is no benefit to keeping these separate and if we were to use the same object for both, then the configuration file itself could specify certain options that override the defaults. This would allow a module have a different vendor while allowing the user to make less potential modifications.
Making this modification does not alter the usability or API.
Currently module configuration is separated into 2 parts. One for the configuration that configures the object and one that contains custom parameters specified by a configuration file.
There is no benefit to keeping these separate and if we were to use the same object for both, then the configuration file itself could specify certain options that override the defaults. This would allow a module have a different vendor while allowing the user to make less potential modifications.
Making this modification does not alter the usability or API.