Experimental UI plugin system

[baransu]

Experimental UI plugin support. Your plugin has to be build using epl-scripts or ejected version of epl-scripts exporting optional parts:

• Component - view of your plugin
• name - epl-your-plugin-name
• icon - font-awesome icon for navigation bar
• reducer - redux reducer for access to whole UI state

To add any custom plugin you have to add it as node dependency npm/yarn install https://link/to/your/plugin.git and add it to plugins list in package.json. These plugins will be built into UI bundle.

There are also options to add plugins in development or how to develop plugins but I'm not going to create documentation for it as well as documentation about whole plugin system until it's finished and o longer experimental.

[arkgil]

Is is possible to includes dependencies form file system paths?

[baransu]

@michalslaski @arkgil You can test it out by runningyarn build first to check that there is no plugin available, and then:

yarn add https://github.com/Baransu/epl-plugin.git

Then you can check if epl-plugin is specified in plugins list in package.json. If everything went correct you can yarn build and run build folder on simple any simple http-server (e.g. http-server) .

[baransu]

@arkgil Yes. you can use yarn link or yarn add file:path/to/plugin

EDIT: Here you can read about yarn link: https://yarnpkg.com/lang/en/docs/cli/link/