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
It's a bit of a stability/security concern to let plugins return potentially non-compliant objects that are used in the framework. The parseModule() handler should instead return a module config that can be validated, potentially with a free-form key that can be passed back to plugin action handlers.
Plugins would then be responsible for upgrading basic Module objects to more specific subclasses, or we could perhaps add some convenience feature for doing that automatically before passing to action handlers.
The text was updated successfully, but these errors were encountered:
It's a bit of a stability/security concern to let plugins return potentially non-compliant objects that are used in the framework. The
parseModule()
handler should instead return a module config that can be validated, potentially with a free-form key that can be passed back to plugin action handlers.Plugins would then be responsible for upgrading basic
Module
objects to more specific subclasses, or we could perhaps add some convenience feature for doing that automatically before passing to action handlers.The text was updated successfully, but these errors were encountered: