This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Plugin system #25
Labels
Comments
Can you please explain |
This is concept borrowed from create-react-app. This will remove one dependency ( |
|
Thanks, now I understand :) Sounds good 👍 |
I'm going to merge experimental plugin system as fast as possible because we want to merge |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue is an umbrella issue for Erlang Performance Lab UI plugin system.
We're working on plugin system which will provide other developers easy way for creating new functionality for Erlang Performance Lab.
Our key part are
epl-scripts
. This is Node dependency providing dev, build and test functionality for every plugin. It's preconfigured blackbox with all required parts for new EPL plugin development. Because by defaultepl-scripts
are preconfigured we support almost none additional configuration. But there comeseject
functionality. You can eject your project which move allepl-scripts
config and scripts into your project. This allow you to tweak configs and/or add custom functionality which we don't support. This is one way path. You cannot revert ejection.Another part are
epl-components
. This dependency will provide styled component for building new EPL views as well as some helper functions for socket connection, Footer and Menu API, etc.Both
epl-scripts
andepl-components
will be published to npm.erlangpl-ui
will require some refactoring to allow plugins loading in both development mode as well as production mode. In later phase we're thinking about loading additional plugins at runtime, but this may change in the future.epl-scripts
epl-components
To be defained
erlangpl-ui
The text was updated successfully, but these errors were encountered: