-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
Extract plugin handling in a PluginRegistry
class independent of the Application
#703
Extract plugin handling in a PluginRegistry
class independent of the Application
#703
Conversation
cc @Zsailer |
eb66b9b
to
6f0a921
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @fcollonval, LGTM, at least everything work in a dev installation.
I just have a few comments.
packages/coreutils/src/typing.d.ts
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of curiosity, why do we need this ?
Should it be defined in other packages using console
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This package is compatible for browser and nodejs environment.
The automatic way to make TypeScript happy is to mention in the tsconfig that the target is DOM
. However node js does not implement all the DOM API. But it does implement the console. So this pleases TypeScript but prevent future change to reference for example window
or document
(not available in node js).
Co-authored-by: Nicolas Brichet <32258950+brichet@users.noreply.github.com>
Thanks for the review @brichet |
Fixes #697
Fixes #586
Refactor the plugins handling outside of the
Application
class to be able to instantiate and use it independently.Add a allowed/blocked list feature to the new class.
The new
PluginRegistry
class is defined in coreutils to avoid bringing the widgets package in the stack dependency of the plugin system consumer. That implies adding the algorithm package as dependency to coreutils.