dry_crud 5.2.0 → 6.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3fa4767cf781b94a5ed47a5833f76a96494c450967e9f3599806226aafcf4a74
-  data.tar.gz: bd4c40f8493eef40c6618ead701877f8ec8d39b552db5787ae184273be0fc8d3
+  metadata.gz: 3ff2a042dc7c846957d5e17001f9a538df726084e3695988d68066849938d544
+  data.tar.gz: 504a97b4e2b0769cb260790725bb1a59aaffe33a16a093556d9462dd2403794f
 SHA512:
-  metadata.gz: 8fef4d2ed06521eafd92c4fa87a36d07fdeee79a1a0f0d3a0e6098e2ac98b6c92d7c5cd2e87046b4cf37a3fa2e90f2d1cda382d645e828b3aeba2b5cd26e0903
-  data.tar.gz: 41b31166a4f5c82374587e49fe76580d32487ccff0fa52b6f0e72f131b2eb9a7d296d6ff53d8cc3de470fe1671dbdfb2749a4bdba685ce2bf110ea163abea225
+  metadata.gz: 9808508def34a37d4d7bea43c5e7d810a4ac57d09c36ceadf8ee0fbf5bba3650611c5e3c5b010f5aa015666076ac3971fe824f2d6deeb17d913cc4404d2261bd
+  data.tar.gz: c9b52ac7b06f5ab74f4fc3b8b0f340f1e3e5f35296296d109585dcb51906b46eb9615c393865cdde30aefb096dabf41dac197a24dc8e364d57e071551fbb0e5e

data/README.rdoc

@@ -1,6 +1,6 @@
 = DRY CRUD
 
-{<img src="https://secure.travis-ci.org/codez/dry_crud.png" />}[http://travis-ci.org/codez/dry_crud]
+{<img src="https://travis-ci.org/codez/dry_crud.svg?branch=master" />}[http://travis-ci.org/codez/dry_crud]
 
 dry_crud generates simple and extendable controllers, views and helpers that support you to DRY up the CRUD code in your Rails projects. List, search, sort, show, create, edit and destroy any model entries in just 5 minutes. Start with these artifacts and build a clean base to efficiently develop your application upon.
 
@@ -21,7 +21,7 @@ We recommend to use dry_crud as a generator as described above for the best unde
 
   rails generate dry_crud:file list/index.html.erb
 
-If a dry_crud file exists in your application, it will be used, if not, the one from the engine is used. This holds for controllers, helpers and view templates.
+If a dry_crud file exists in your application, it will be used, if not, the one from the engine is used. This holds for controllers, helper methods and view templates.
 
 
 == Integration
@@ -33,12 +33,12 @@ To integrate dry_crud into your code, only a few additions are required:
 * Optionally define a +list+ scope in your models to be used in the +index+ action.
 * Optionally define a +options_list+ scope in your models to be used in select dropdowns.
 
-From version 5.0 onwards, the major and minor version numbers will be kept in sync with Rails, and only the matching Rails version is supported. Version 3.0 is compatible 4.2, Version 2.0 and higher are compatible with Rails 4 and Rails 3.2. dry_crud is tested with Ruby 2.2.5 and JRuby. If you are using Ruby 1.9.3, please refer to version 3.0.0.
+From version 5.0 onwards, the major and minor version numbers will be kept in sync with Rails, and only the matching Rails version is supported. Version 3.0 is compatible 4.2, Version 2.0 and higher are compatible with Rails 4 and Rails 3.2. dry_crud is tested with Ruby 2.5. If you are using Ruby 1.9.3, please refer to version 3.0.0.
 
 
 == Background
 
-In most Rails applications, you have some models that require basic CRUD (create, read, update, delete) functionality. There are various possibilities like Rails scaffolding, {Inherited Resources}[https://github.com/josevalim/inherited_resources] or {Rails Admin}[https://github.com/sferik/rails_admin]. Still, various parts in your application remain duplicated. While you might pull up common methods into a common superclass controller, most views still contain very similar code. And then you also have to remember the entire API of these frameworks.
+In most Rails applications, you have some models that require basic CRUD (create, read, update, delete) functionality. There are various possibilities like Rails scaffolding, {Inherited Resources}[https://github.com/activeadmin/inherited_resources] or {Rails Admin}[https://github.com/sferik/rails_admin]. Still, various parts in your application remain duplicated. While you might pull up common methods into a common superclass controller, most views still contain very similar code. And then you also have to remember the entire API of these frameworks.
 
 Enter dry_crud.
 
@@ -46,11 +46,11 @@ Enter dry_crud.
 The main idea of dry_crud is to concentrate basic functionality of your application, like CRUD actions, uniform formatting, forms and tables into specifically extendable units. dry_crud generates various foundation classes that you may browse easily and adapt freely to your application's needs. For each model, you may transparently customize arbitrary parts or just fallback to the general behavior. This applies not only for controllers, but also for view templates and helpers. There is no black box your code depends on. You lay the foundation that fits your application best.
 </b>
 
-dry_crud is a Rails generator. All code resides in your application and is open for you to inspect and to extend. You may pick whatever you consider useful or adapt what is not sufficient. Even if you do not require any CRUD functionality, you might find some helpers simplifying your work. There are no runtime dependencies to the dry_crud gem. Having said this, dry_crud does not want to provide a maximum of functionality that requires a lot of configuration, but rather a clean and lightweight foundation to build your application's requirements upon. This is why dry_crud comes as a generator and not as a Rails plugin.
+dry_crud is a Rails generator. All code resides in your application and is open for you to inspect and to extend. You may pick whatever you consider useful or adapt what is not sufficient. Even if you do not require any CRUD functionality, you might find some helpers simplifying your work. There are no runtime dependencies to the dry_crud gem. Having said this, dry_crud does not want to provide a maximum of functionality that requires a lot of configuration, but rather a clean and lightweight foundation to build your application's requirements upon. This is why dry_crud comes as a generator and not as a Rails extension.
 
-dry_crud does not depend on any other plugins, but easily allows you to integrate them in order to unify the behavior of your CRUD controllers. You might even use the plugins mentioned above to adapt your generated CrudController base class. All classes come with thorough tests that provide you with a solid foundation for implementing your own adaptions.
+dry_crud does not depend on any other gems, but easily allows you to integrate them in order to unify the behavior of your CRUD controllers. You might even use the gems mentioned above to adapt your generated CrudController base class. All classes come with thorough tests that provide you with a solid foundation for implementing your own adaptions.
 
-A basic CSS gets you started with your application's layout. For advanced needs, dry_crud supports the styles and classes used in {Bootstrap 3}[http://getbootstrap.com]. A great design never was so close.
+A basic CSS gets you started with your application's layout. For advanced needs, dry_crud supports the styles and classes used in {Bootstrap 4}[http://getbootstrap.com]. A great design never was so close.
 
 If you find yourself adapting the same parts of dry_crud for your applications over and over, please feel free to {fork me on Github}[http://github.com/codez/dry_crud].
 
@@ -66,7 +66,7 @@ Say you want to manage a +Person+ model. Overwrite the +to_s+ method of your mod
 <tt>app/models/person.rb</tt>:
   class Person
     def to_s
-      "#{lastname} #{firstname}"
+      [lastname, firstname].compact.join(' ')
     end
   end
 
@@ -74,7 +74,7 @@ Then create the following controller. The +permitted_attrs+ define the attribute
 
 <tt>app/controllers/people_controller.rb</tt>:
   class PeopleController < CrudController
-    self.permitted_attrs = [:firstname, :lastname, :birthday, :sex, :city_id]
+    self.permitted_attrs = [:firstname, :lastname, :birthday, :gender, :city_id]
   end
 
 That's it. You have a sortable overview of all people, detail pages and forms to edit and create people. Of course, you may delete people as well. By default, all attributes are displayed and formatted according to their column type wherever they appear. This applies for the input fields as well.
@@ -84,14 +84,14 @@ That's it. You have a sortable overview of all people, detail pages and forms to
 
 Well, maybe there are certain attributes you do not want to display in the people list, or others that are not editable in the form. No problem, simply create a <tt> _list</tt> partial in <tt>app/views/people/_list.html.erb</tt> to customize this:
 
-  <%= crud_table :lastname, :firstname, :city, :sex %>
+  <%= crud_table :lastname, :firstname, :city, :gender %>
 
 This only displays these four attributes in the table. All other templates, as well as the main index view, fallback to the ones in <tt>app/views/crud</tt>.
 
 
 ==== Adapt general behavior
 
-Next, let's adapt a part of the general behavior used in all CRUD controllers. As an example, we include pagination with kaminari[https://github.com/amatsuda/kaminari] in all our overview tables:
+Next, let's adapt a part of the general behavior used in all CRUD controllers. As an example, we include pagination with kaminari[https://github.com/kaminari/kaminari] in all our overview tables:
 
 In <tt>app/controllers/list_controller.rb</tt>, change the list_entries method to
   def list_entries
@@ -106,11 +106,11 @@ And we are done. All our controllers inheriting from ListController, including a
 
 ==== Special formatting for selected attributes
 
-Sometimes, the default formatting provided by +format_attr+ will not be sufficient. We have a boolean column +sex+ in our model, but would like to display 'male' or 'female' for it (instead of 'no' or 'yes', which is a bit cryptic). Just define a method in your view helper starting with <tt>format_</tt>, followed by the class and attribute name:
+Sometimes, the default formatting provided by +format_attr+ will not be sufficient. We have a boolean column +female+ in our model (which is quite a legacy nowadays!), but we would like to display 'male' or 'female' for it (instead of 'no' or 'yes', which is a bit cryptic). Just define a method in your view helper starting with <tt>format_</tt>, followed by the class and attribute name:
 
 In <tt>app/helpers/people.rb</tt>:
-  def format_person_sex(person)
-    person.sex ? 'female' : 'male'
+  def format_person_female(person)
+    person.female ? 'female' : 'male'
   end
 
 Should you have attributes with the same name for multiple models that you want to be formatted the same way, you may define a helper method <tt>format_{attr}</tt> for these attributes.
@@ -133,7 +133,7 @@ In <tt>app/controllers/people_controller.rb</tt>:
 When you display computed values in your list table, you may define sort mappings to enable sorting of these columns:
 
 In <tt>app/controllers/people_controller.rb</tt>:
-  self.sort_mappings = {age: 'birthday', city_id: 'cities.name'}
+  self.sort_mappings = { age: 'birthday', city_id: 'cities.name' }
 
 There is also a simple search functionality (based on SQL LIKE queries) implemented in Crud::Searchable. Define an array of columns in your controller's +search_columns+ class variable to make the entries searchable by these fields:
 
@@ -151,17 +151,17 @@ dry_crud provides two builder classes for update/create forms and tables for dis
 
 The following code defines a table with some attribute columns for a list of same-type entries. Columns get a header corresponding to the attribute name:
   <%= plain_table(@people) do |t|
-        t.sortable_attrs :lastname, :firstname
+        t.sortable_attrs(:lastname, :firstname)
       end %>
 
 If entries is empty, a basic 'No entries found' message is rendered instead of the table.
 
 To render custom columns, use the +col+ method with an appropriate block:
   <%= plain_table(@people) do |t|
-        t.sortable_attrs :lastname, :firstname
-        t.col('', class: 'center') {|entry| image_tag(entry.picture) }
-        t.attr :street
-        t.col('Map') {|entry| link_to(entry.city, "http://maps.google.com/?q=#{entry.city}" }
+        t.sortable_attrs(:lastname, :firstname)
+        t.col('', class: 'center') { |entry| image_tag(entry.picture) }
+        t.attr(:street)
+        t.col('Map') { |entry| link_to(entry.city, "http://maps.google.com/?q=#{entry.city}" }
       end %>
 
 For views of subclasses of ListController, you can directly use the +crud_table+ helper method, where you do not have to pass the <tt>@people</tt> list explicitly and actions are added automatically.
@@ -175,9 +175,9 @@ Forms work very similar. In the most simple case, you just have to specify which
 Of course, custom input fields may be defined as well:
   <%= standard_form(@person, url: custom_update_person_path(@person.id)) do |f| %>
     <%= f.labeled_input_fields :firstname, :lastname %>
-    <%= f.labeled(:sex) do %>
-      <%= f.radio_button :sex, true %> female
-      <%= f.radio_button :sex, false %> male
+    <%= f.labeled(:female) do %>
+      <%= f.radio_button :female, true %> female
+      <%= f.radio_button :female, false %> male
     <% end %>
     <%= f.labeled_integer_field :age %>
     <%= f.labeled_file_field :picture %>
@@ -193,7 +193,7 @@ Optionally, +has_and_belongs_to_many+ and +has_many+ associations can be rendere
 
 And yes again, the same advice for where to put finder logic applies here as well.
 
-<b>Note:</b> +has_and_belongs_to_many+ and +has_many+ associations are not automatically rendered in a form, you have to explicitly include these attributes. You might also want to stylize the multi-select widget, for example with a {jQuery UI Multiselect}[http://www.quasipartikel.at/multiselect/].
+<b>Note:</b> +has_and_belongs_to_many+ and +has_many+ associations are not automatically rendered in a form, you have to explicitly include these attributes. You might also want to stylize the multi-select widget with a JavaScript library of your choice.
 
 
 === Nested Resources
@@ -221,8 +221,8 @@ In <tt>app/controllers/people_controller.rb</tt>:
 
   def delete_picture
     if !perform_delete_picture(entry.picture)
-      flash.alert = 'Could not delete picture'
-      false
+      flash[:alert] = 'Could not delete picture'
+      throw :abort
     end
   end
 
@@ -269,49 +269,49 @@ All generated files are supposed to provide a reasonable foundation for the CRUD
 
 === Controller
 
-{controller/crud_controller.rb}[http://codez.ch/dry_crud?q=CrudController]:: Abstract controller providing basic CRUD actions. This implementation mainly follows the one of the Rails scaffolding controller and responses to HTML and JSON requests. Some enhancements were made to ease extendability. Several protected helper methods are there to be (optionally) overriden by subclasses. With the help of additional callbacks, it is possible to hook into the action procedures without overriding the entire method. This class is based on ListController.
+{controller/crud_controller.rb}[https://rubydoc.info/github/codez/dry_crud/master/CrudController]:: Abstract controller providing basic CRUD actions. This implementation mainly follows the one of the Rails scaffolding controller and responses to HTML and JSON requests. Some enhancements were made to ease extendability. Several protected helper methods are there to be (optionally) overriden by subclasses. With the help of additional callbacks, it is possible to hook into the action procedures without overriding the entire method. This class is based on ListController.
 
-{controller/list_controller.rb}[http://codez.ch/dry_crud?q=ListController]:: Abstract controller providing a basic list action. Use this controller if you require read-only functionality. It includes the following modules.
+{controller/list_controller.rb}[https://rubydoc.info/github/codez/dry_crud/master/ListController]:: Abstract controller providing a basic list action. Use this controller if you require read-only functionality. It includes the following modules.
 
-{controller/dry_crud/generic_model.rb}[http://codez.ch/dry_crud?q=DryCrud::GenericModel]:: Work with the model whose name corrsponds to the controller's name.
+{controller/dry_crud/generic_model.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/GenericModel]:: Work with the model whose name corrsponds to the controller's name.
 
-{controller/dry_crud/nestable.rb}[http://codez.ch/dry_crud?q=DryCrud::Nestable]:: Provides functionality to easily nest controllers/resources.
+{controller/dry_crud/nestable.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/Nestable]:: Provides functionality to easily nest controllers/resources.
 
-{controller/dry_crud/rememberable.rb}[http://codez.ch/dry_crud?q=DryCrud::Rememberable]:: Remembers certain params of the index action in order to return to the same list after an entry was viewed or edited.
+{controller/dry_crud/rememberable.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/Rememberable]:: Remembers certain params of the index action in order to return to the same list after an entry was viewed or edited.
 
-{controller/dry_crud/searchable.rb}[http://codez.ch/dry_crud?q=DryCrud::Searchable]:: Search functionality for the index table.
+{controller/dry_crud/searchable.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/Searchable]:: Search functionality for the index table.
 
-{controller/dry_crud/sortable.rb}[http://codez.ch/dry_crud?q=DryCrud::Sortable]:: Sort functionality for the index table.
+{controller/dry_crud/sortable.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/Sortable]:: Sort functionality for the index table.
 
-{controller/dry_crud/render_callbacks.rb}[http://codez.ch/dry_crud?q=DryCrud::RenderCallbacks]:: Provide +before_render+ callbacks to controllers.
+{controller/dry_crud/render_callbacks.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/RenderCallbacks]:: Provide +before_render+ callbacks to controllers.
 
-{controller/dry_crud/responder.rb}[http://codez.ch/dry_crud?q=DryCrud::Responder]:: Responder used by the CrudController to handle the +path_args+.
+{controller/dry_crud/responder.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/Responder]:: Responder used by the CrudController to handle the +path_args+.
 
 === Helpers
 
-{helpers/dry_crud/form/builder.rb}[http://codez.ch/dry_crud?q=DryCrud::Form::Builder]:: A form builder that automatically selects the corresponding input type for ActiveRecord columns. Input elements are rendered together with a label by default.
+{helpers/dry_crud/form/builder.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/Form/Builder]:: A form builder that automatically selects the corresponding input type for ActiveRecord columns. Input elements are rendered together with a label by default.
 
-{helpers/dry_crud/form/control.rb}[http://codez.ch/dry_crud?q=DryCrud::Form::Control]:: Representation of a single form control consisting of a label, input field, addon or help text.
+{helpers/dry_crud/form/control.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/Form/Control]:: Representation of a single form control consisting of a label, input field, addon or help text.
 
-{helpers/dry_crud/table/builder.rb}[http://codez.ch/dry_crud?q=DryCrud::Table::Builder]:: A helper object to easily define tables listing several rows of the same data type.
+{helpers/dry_crud/table/builder.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/Table/Builder]:: A helper object to easily define tables listing several rows of the same data type.
 
-{helpers/dry_crud/table/col.rb}[http://codez.ch/dry_crud?q=DryCrud::Table::Col]:: Helper class representing a single table column.
+{helpers/dry_crud/table/col.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/Table/Col]:: Helper class representing a single table column.
 
-{helpers/dry_crud/table/actions.rb}[http://codez.ch/dry_crud?q=DryCrud::Table::Actions]:: Module to add support for uniform CRUD actions in tables.
+{helpers/dry_crud/table/actions.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/Table/Actions]:: Module to add support for uniform CRUD actions in tables.
 
-{helpers/dry_crud/table/sorting.rb}[http://codez.ch/dry_crud?q=DryCrud::Table::Sorting]:: Module to add support for sort links in table headers.
+{helpers/dry_crud/table/sorting.rb}[https://rubydoc.info/github/codez/dry_crud/master/DryCrud/Table/Sorting]:: Module to add support for sort links in table headers.
 
-{helpers/form_helper.rb}[http://codez.ch/dry_crud?q=FormHelper]:: Create forms to edit models with Crud::FormBuilder. Contains a standardized and a custom definable form.
+{helpers/form_helper.rb}[https://rubydoc.info/github/codez/dry_crud/master/FormHelper]:: Create forms to edit models with Crud::FormBuilder. Contains a standardized and a custom definable form.
 
-{helpers/table_helper.rb}[http://codez.ch/dry_crud?q=TableHelper]:: Create tables to list multiple models with Crud::TableBuilder. Contains a standardized and a custom definable table.
+{helpers/table_helper.rb}[https://rubydoc.info/github/codez/dry_crud/master/TableHelper]:: Create tables to list multiple models with Crud::TableBuilder. Contains a standardized and a custom definable table.
 
-{helpers/format_helper.rb}[http://codez.ch/dry_crud?q=FormatHelper]:: Format attribute and basic values according to their database or Ruby type.
+{helpers/format_helper.rb}[https://rubydoc.info/github/codez/dry_crud/master/FormatHelper]:: Format attribute and basic values according to their database or Ruby type.
 
-{helpers/actions_helper.rb}[http://codez.ch/dry_crud?q=ActionsHelper]:: Uniform action links for the most common crud actions.
+{helpers/actions_helper.rb}[https://rubydoc.info/github/codez/dry_crud/master/ActionsHelper]:: Uniform action links for the most common crud actions.
 
-{helpers/i18n_helper.rb}[http://codez.ch/dry_crud?q=I18nHelper]:: Translation helpers extending Rails' +translate+ helper to support translation inheritance over the controller class hierarchy.
+{helpers/i18n_helper.rb}[https://rubydoc.info/github/codez/dry_crud/master/I18nHelper]:: Translation helpers extending Rails' +translate+ helper to support translation inheritance over the controller class hierarchy.
 
-{helpers/utility_helper.rb}[http://codez.ch/dry_crud?q=UtilityHelper]:: View helpers for basic functions used in various other helpers.
+{helpers/utility_helper.rb}[https://rubydoc.info/github/codez/dry_crud/master/UtilityHelper]:: View helpers for basic functions used in various other helpers.
 
 
 
@@ -372,9 +372,9 @@ app/assets/images/action/*.png:: Some sample action icons from the {Open Icon Li
 
 test/support/crud_test_model.rb:: A dummy model to run CRUD tests against.
 
-{test/support/custom_assertions.rb}[http://codez.ch/dry_crud?q=CustomAssertions]:: A handful of convenient assertions. Include this module into your <tt>test_helper.rb</tt> file.
+{test/support/custom_assertions.rb}[https://rubydoc.info/github/codez/dry_crud/master/CustomAssertions]:: A handful of convenient assertions. Include this module into your <tt>test_helper.rb</tt> file.
 
-{test/support/crud_controller_test_helper.rb}[http://codez.ch/dry_crud?q=CrudControllerTestHelper]:: A module to include into the functional tests for your CrudController subclasses. Contains a handful of CRUD functionality tests for the provided implementation. So for each new CRUD controller, you get 20 tests for free.
+{test/support/crud_controller_test_helper.rb}[https://rubydoc.info/github/codez/dry_crud/master/CrudControllerTestHelper]:: A module to include into the functional tests for your CrudController subclasses. Contains a handful of CRUD functionality tests for the provided implementation. So for each new CRUD controller, you get 20 tests for free.
 
 test/controllers/crud_test_models_controller_test.rb:: Functional tests for the basic CrudController functionality.
 
@@ -385,7 +385,7 @@ test/helpers/*_test.rb:: Tests for the provided helper implementations and a gre
 
 spec/support/crud_controller_examples.rb:: A whole set of shared exampled to include into your controller specs. See <tt>spec/controllers/crud_test_models_controller_spec.rb</tt> for usage. So for each new CRUD controller, you get all the basic specs for free.
 
-{spec/support/crud_controller_test_helper.rb}[http://codez.ch/dry_crud?q=CrudControllerTestHelper::ClassMethods]:: Convenience methods used by the crud controller examples.
+{spec/support/crud_controller_test_helper.rb}[https://rubydoc.info/github/codez/dry_crud/master/CrudControllerTestHelper/ClassMethods]:: Convenience methods used by the crud controller examples.
 
 spec/support/crud_test_model.rb:: A dummy model to run CRUD tests against.
 

data/VERSION

@@ -1 +1 @@
-5.2.0
+6.0.0

data/app/helpers/dry_crud/form/builder.rb

@@ -73,9 +73,7 @@ module DryCrud
       def boolean_field(attr, html_options = {})
         content_tag(:div, class: 'checkbox') do
           content_tag(:label) do
-            # rubocop:disable Rails/OutputSafety
             detail = html_options.delete(:detail) || ' '.html_safe
-            # rubocop:enable Rails/OutputSafety
             safe_join([check_box(attr, html_options), ' ', detail])
           end
         end
@@ -90,6 +88,22 @@ module DryCrud
         end
       end
 
+      def integer_field(attr, html_options = {})
+        html_options[:step] ||= 1
+        number_field(attr, html_options)
+      end
+
+      def float_field(attr, html_options = {})
+        html_options[:step] ||= 'any'
+        number_field(attr, html_options)
+      end
+
+      def decimal_field(attr, html_options = {})
+        html_options[:step] ||=
+          (10**-column_property(object, attr, :scale)).to_f
+        number_field(attr, html_options)
+      end
+
       # Customize the standard text area to have 5 rows by default.
       def text_area(attr, html_options = {})
         add_css_class(html_options, 'form-control')
@@ -97,10 +111,6 @@ module DryCrud
         super(attr, html_options)
       end
 
-      alias integer_field number_field
-      alias float_field number_field
-      alias decimal_field number_field
-
       # Render a select element for a :belongs_to association defined by attr.
       # Use additional html_options for the select element.
       # To pass a custom element list, specify the list with the :list key or

data/app/helpers/utility_helper.rb

@@ -3,9 +3,8 @@ require 'English'
 # View helpers for basic functions used in various other helpers.
 module UtilityHelper
 
-  # rubocop:disable Rails/OutputSafety
-  EMPTY_STRING = ' '.html_safe # non-breaking space asserts better css.
-  # rubocop:enable Rails/OutputSafety
+  # non-breaking space asserts better css.
+  EMPTY_STRING = ' '.html_safe.freeze
 
   # Render a content tag with the collected contents rendered
   # by &block for each item in collection.

data/app/views/layouts/application.html.erb

@@ -7,9 +7,10 @@
 
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
   <%= csrf_meta_tag %>
+  <%= csp_meta_tag %>
 
-  <%= stylesheet_link_tag 'application', media: 'all', 'data-turbolinks-track' => true %>
-  <%= javascript_include_tag 'application', 'data-turbolinks-track' => true %>
+  <%= stylesheet_link_tag 'application', media: 'all', 'data-turbolinks-track': 'reload' %>
+  <%= javascript_pack_tag 'application', 'data-turbolinks-track': 'reload' %>
 
   <%= yield :head %>
 </head>

data/app/views/layouts/application.html.haml

@@ -9,9 +9,10 @@
 
     %meta{name: 'viewport', content: 'width=device-width, initial-scale=1.0'}
     = csrf_meta_tag
+    = csp_meta_tag
 
-    = stylesheet_link_tag 'application', :media => 'all', 'data-turbolinks-track' => true
-    = javascript_include_tag 'application', 'data-turbolinks-track' => true
+    = stylesheet_link_tag 'application', :media => 'all', 'data-turbolinks-track': 'reload'
+    = javascript_pack_tag 'application', 'data-turbolinks-track': 'reload'
 
     = yield :head
 

data/lib/dry_crud/engine.rb

@@ -1,14 +1,17 @@
 module DryCrud
   # Dry Crud Rails engine
   class Engine < Rails::Engine
+
+    # Fields with errors are directly styled in DryCrud::FormBuilder.
+    # Rails should just output the plain html tag.
     initializer 'dry_crud.field_error_proc' do |_app|
-      # Fields with errors are directly styled in DryCrud::FormBuilder.
-      # Rails should just output the plain html tag.
       ActionView::Base.field_error_proc =
         proc { |html_tag, _instance| html_tag }
+    end
 
-      # Load dry_crud engine helpers first so that the application may override
-      # them.
+    # Load dry_crud engine helpers first so that the application may override
+    # them.
+    config.to_prepare do
       paths = ApplicationController.helpers_path
       helper_path = "#{File::SEPARATOR}app#{File::SEPARATOR}helpers"
       regexp = /dry_crud(-\d+\.\d+\.\d+)?#{helper_path}\z/
@@ -18,5 +21,6 @@ module DryCrud
         paths.prepend(dry_crud_helpers)
       end
     end
+
   end
 end

data/lib/generators/dry_crud/dry_crud_generator.rb

@@ -1,6 +1,6 @@
 begin
   require 'generators/dry_crud/dry_crud_generator_base'
-rescue LoadError => _ # rubocop:disable Lint/HandleExceptions
+rescue LoadError => _e # rubocop:disable Lint/HandleExceptions
   # ok, we are in the rake task
 end
 

data/lib/generators/dry_crud/templates/spec/support/crud_controller_examples.rb

@@ -43,11 +43,9 @@ shared_examples 'crud controller' do |options|
 
   describe_action :get, :index,
                   unless: skip?(options, 'index') do
-
     context '.html',
             format: :html,
             unless: skip?(options, %w[index html]) do
-
       context 'plain',
               unless: skip?(options, %w[index html plain]),
               combine: 'ihp' do
@@ -110,11 +108,9 @@ shared_examples 'crud controller' do |options|
   describe_action :get, :show,
                   id: true,
                   unless: skip?(options, 'show') do
-
     context '.html',
             format: :html,
             unless: skip?(options, %w[show html]) do
-
       context 'plain',
               unless: skip?(options, %w[show html plain]),
               combine: 'sh' do
@@ -254,7 +250,6 @@ shared_examples 'crud controller' do |options|
     context '.json',
             format: :json,
             unless: skip?(options, %w[update json]) do
-
       context 'with valid params',
               unless: skip?(options, %w[update json valid]),
               combine: 'ujv' do
@@ -278,7 +273,6 @@ shared_examples 'crud controller' do |options|
   describe_action :delete, :destroy,
                   id: true,
                   unless: skip?(options, %w[destroy]) do
-
     it 'removes entry from database', perform_request: false do
       expect { perform_request }.to change { model_class.count }.by(-1)
     end
@@ -286,7 +280,6 @@ shared_examples 'crud controller' do |options|
     context '.html',
             format: :html,
             unless: skip?(options, %w[destroy html]) do
-
       context 'successfull', combine: 'dhs' do
         it_is_expected_to_redirect_to_index
         it_is_expected_to_have_flash(:notice)
@@ -301,7 +294,6 @@ shared_examples 'crud controller' do |options|
     context '.json',
             format: :json,
             unless: skip?(options, %w[destroy json]) do
-
       context 'successfull', combine: 'djs' do
         it_is_expected_to_respond(204)
         it { expect(response.body).to be_blank }

data/lib/generators/dry_crud/templates/spec/support/crud_controller_test_helper.rb

@@ -45,7 +45,7 @@ module CrudControllerTestHelper
 
     # treat in-memory entry as committed in order to
     # avoid rollback of internal state.
-    entry.committed! if entry
+    entry&.committed!
   end
 
   def restore_request

data/lib/generators/dry_crud/templates/test/support/crud_test_helper.rb

@@ -1,8 +1,8 @@
 #:nodoc:
-REGEXP_ROWS = /<tr.+?<\/tr>/m #:nodoc:
-REGEXP_HEADERS = /<th.+?<\/th>/m #:nodoc:
-REGEXP_SORT_HEADERS = /<th.*?><a .*?sort_dir=asc.*?>.*?<\/a><\/th>/m #:nodoc:
-REGEXP_ACTION_CELL = /<td class=\"action\"><a .*?href.+?<\/a><\/td>/m #:nodoc:
+REGEXP_ROWS = /<tr.+?<\/tr>/m.freeze
+REGEXP_HEADERS = /<th.+?<\/th>/m.freeze
+REGEXP_SORT_HEADERS = /<th.*?><a .*?sort_dir=asc.*?>.*?<\/a><\/th>/m.freeze
+REGEXP_ACTION_CELL = /<td class=\"action\"><a .*?href.+?<\/a><\/td>/m.freeze
 
 # A simple test helper to prepare the test database with a CrudTestModel model.
 # This helper is used to test the CrudController and various helpers
@@ -128,8 +128,17 @@ module CrudTestHelper
     routes = @routes
 
     controller.singleton_class.send(:include, routes.url_helpers)
-    controller.view_context_class = Class.new(controller.view_context_class) do
-      include routes.url_helpers
+
+    if controller.respond_to?(:view_context_class)
+      view_context_class = Class.new(controller.view_context_class) do
+        include routes.url_helpers
+      end
+      custom_view_context = Module.new do
+        define_method(:view_context_class) do
+          view_context_class
+        end
+      end
+      controller.extend(custom_view_context)
     end
 
     @routes.draw { resources :crud_test_models }

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: dry_crud
 version: !ruby/object:Gem::Version
-  version: 5.2.0
+  version: 6.0.0
 platform: ruby
 authors:
 - Pascal Zumkehr
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-06-26 00:00:00.000000000 Z
+date: 2019-09-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '5.0'
+        version: '6.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '5.0'
+        version: '6.0'
 description: |
   Generates simple and extendable controller, views and helpers that support you
   to DRY up the CRUD code in your Rails project. Start with these elements and
@@ -139,7 +139,7 @@ files:
 - lib/generators/dry_crud/templates/test/support/crud_test_model.rb
 - lib/generators/dry_crud/templates/test/support/crud_test_models_controller.rb
 - lib/generators/dry_crud/templates/test/support/custom_assertions.rb
-homepage: http://codez.ch/dry_crud
+homepage: http://github.com/codez/dry_crud
 licenses: []
 metadata: {}
 post_install_message: