New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a way to configure which plugins to use #57

sh00s opened this Issue Nov 12, 2018 · 0 comments


None yet
1 participant
Copy link

sh00s commented Nov 12, 2018

Currently if multiple plugins are loaded of the same type (aside from built-in plugins and plugins that allow multiple active instances of the same types - e.g. ConfigSources), PluginRegistry will fail, as it doesn't have a way to decide which one of those to use.

Instead it should be configurable (via settings or via the configuration file) which plugin to use for each plugin type. Then PluginRegistry::setCurrentSinglePlugins() should use that information to pick the active plugin:

void PluginRegistry::setCurrentSinglePlugins() {
// TODO: pick plugins based on configuration. For now this just picks the
// only plugin available or the only one that's not built-in if there is
// a built-in and a loaded one

It should also subscribe to config/setting changes so that you can reconfigure which plugin to use on the fly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment