Right now the existing plugins are located in the same Rails engine. After discussing in the office we've decided to split them in one-engine per plugin, reasons are:
Keep plugins independent
Avoid having to install them for a client that does not need them
These plugins share both JS and Ruby code (for test helpers). In order to share this between them one idea was to create a gem, but it's open to other solutions.
In regard to frontend integration, each plugin implements a Vue component named <plugin_name>.vue. Move the plugins from app/javascript/gobierto_plans/plugins/*.vue to the vendor directory. plan_types_controller uses a relative path to load the plugins, keep that in mind.
Right now the existing plugins are located in the same Rails engine. After discussing in the office we've decided to split them in one-engine per plugin, reasons are:
These plugins share both JS and Ruby code (for test helpers). In order to share this between them one idea was to create a gem, but it's open to other solutions.
In regard to frontend integration, each plugin implements a Vue component named
<plugin_name>.vue
. Move the plugins fromapp/javascript/gobierto_plans/plugins/*.vue
to the vendor directory.plan_types_controller
uses a relative path to load the plugins, keep that in mind.