Open
Description
Sometimes ( emphasis on sometimes ), we may want to disable plugins, or enable dynamic plugins. At runtime.
Currently plugins are merged into the system, and those pieces of the system they introduced cannot be traced back to a plugin.
A usecase for this, is to completely change the ui, in response to something dynamic. I know OAI 3.0 has a mechanism in place, but this could be an alternative approach. And it may server for a use case down the line ( should we bump into one, we can link to this ).
An idea on implementation.
- Each plugin needs a name
- The system is never merged, we create wrapper functions around getBoundActions, getSelects, etc. Such that they get the latest version of a selector/action/reducer, etc. If the plugins aren't merged, we should be able to remove them at runtime - and the wrapper functions mentioned above would continue to work, looking for the next version of an action/selector/reducer.
ping @shockey thoughts