Skip to content
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

Plugin overriding #65

Closed
cart opened this issue Jul 20, 2020 · 0 comments · Fixed by #744
Closed

Plugin overriding #65

cart opened this issue Jul 20, 2020 · 0 comments · Fixed by #744
Labels
A-ECS Entities, components, systems, and events C-Feature A new feature, making something new possible

Comments

@cart
Copy link
Member

cart commented Jul 20, 2020

When initializing an application, most users will probably make a call to add_default_plugins(). This call results in the immediate registration and initialization of all default plugins, and there is no way to unregister or modify the plugin after the fact. It should be possible for users to do any of the following actions:

  • opt out of one or more default plugins, without taking on the responsibility of registering all of the default plugins. (what happens if we add a new default plugin and they forget to add it)
  • change the settings of a default plugin, without taking on the responsibility of registering all of the default plugins. (ex: configuring the default render graph settings in RenderPlugin)

Ideally whatever solution we choose applies to any set of plugins, not just the default ones. It might even be worth formalizing "plugin groups".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-ECS Entities, components, systems, and events C-Feature A new feature, making something new possible
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants