You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, plugins have access to the configurator, and thus the CFG object.
While this permits proper -- per tracim's standards -- configuration, this is not enforced.
We should provide a mechanism that will automatically acquire settings of the plugins through the CFG object and provide them a settings object.
How it works
We could acquire specific attributes in the plugin's class instance
like __name__, config_map or such fields to automatically define it's configuration namespace
We also could enforce that plugins inherits a class that enforces specific attributes and methods that we will use for each loaded plugin.
Related PR
No response
The text was updated successfully, but these errors were encountered:
Feature description
Currently, plugins have access to the configurator, and thus the CFG object.
While this permits proper -- per tracim's standards -- configuration, this is not enforced.
We should provide a mechanism that will automatically acquire settings of the plugins through the CFG object and provide them a settings object.
How it works
We could acquire specific attributes in the plugin's class instance
like
__name__
,config_map
or such fields to automatically define it's configuration namespaceWe also could enforce that plugins inherits a class that enforces specific attributes and methods that we will use for each loaded plugin.
Related PR
No response
The text was updated successfully, but these errors were encountered: