Closed rx closed 3 years ago
:tada: This PR is included in version 3.0.0-beta.1 :tada:
The release is available on:
v3.0.0-beta.1
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 2.1.2 :tada:
The release is available on:
v2.1.2
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 3.0.0-beta.5 :tada:
The release is available on:
v3.0.0-beta.5
Your semantic-release bot :package::rocket:
This is the beta COPRL presenters v3
It includes the native-rails 5 and 6 views and partials. Rework of the plugins to support the above Rename of the module Voom to Coprl
BREAKING CHANGE:
Migrating from Presenters v2 to COPRL Presenters v3
Clients
Voom
=>Coprl
coprl/
Plugins
The plugins have been modified to support Rails native views. There is a generator that you can also use to generate a new plugin:
coprl generate plugin PLUGIN_NAME
. In some cases generating a new plugin and moving over the code may be the preferred option.The rest of this guide assumes you are going to migrate it over manualy.
Module Rename
lib/voom
=> 'lib/coprl'Voom
=>Coprl
lib
files 'voom/' =>coprl/
View Changes
In the Coprl::Presenters::Plugins::PLUGIN_NAME::WebClientComponents Add the following callback that points to your views directory
application
directory under your view directory returned above._
prefix to your templates.erb :"components/event"
=>partial "components/event"
<%= raw File.read(File.expand_path('../../../../../../public/c3.min.css', __dir__) ) %>
Recommended
Move templates, javascript and css files into their own view directory at the root of the presenter. This makes it easier to reason and find the appropriate parts of the plugin