Cocooned

Cocooned makes it easier to handle nested forms in Rails.

Cocooned is form builder-agnostic: it works with standard Rails (>= 7.0, < 8.0) form helpers, Formtastic or SimpleForm.

1. Background
2. Installation
3. Getting started
4. Going further with plugins
5. Links or buttons ?
6. I18n integration
7. JavaScript
8. Styling
9. Migration from a previous version or from Cocoon

Cocooned is a fork of Cocoon by Nathan Van der Auwera. He and all Cocoon contributors did a great job to maintain it for years. Many thanks to them!

However, the project seems to have only received minimal fixes since 2018 and many pull requests, even simple ones, have been on hold for a long time. In 2019, as I needed more than what Cocoon provided at this time, I had the choice to either maintain an extension or to fork it and integrate everything that was waiting and more.

Over the time, Cocooned turned into an almost complete rewrite of Cocoon with more functionnalities, a more fluent API (I hope) and integration with modern toolchains. Still, Cocooned is completely compatible with Cocoon and can be used as a drop-in replacement as long as we talk about Ruby code. Change the name of the gem in your Gemfile and you're done. This compatibility layer with the original Cocoon API will be dropped in the next major release.

On the JavaScript side, Cocooned 2.0 removed the dependency to jQuery (Yeah! 🎉). See JavaScript for details.

Add cocooned to your Gemfile:

gem 'cocooned'

Cocooned comes with an NPM companion package: @notus.sh/cocooned. It bundles JavaScript files to handles in-browser interactions with your nested forms.

If you use import maps (Rails 7.0+ default), add it with:

$ bin/importmap pin @notus.sh/cocooned

If you use Yarn and Webpack (Rails 5.1+ default), add it with:

$ yarn add @notus.sh/cocooned

Note: To ensure you will always get the version of the companion package that match with the gem version, you should specify the same version constraint you used for the cocooned gem in your Gemfile.

Once installed, load it into your application with:

import Cocooned from '@notus.sh/cocooned'
Cocooned.start()

If you still use Sprockets to bundle your javascripts (Rails 3.1+ default), you can either install the companion package from npmjs.org with the package manager of your choice, configure Sprockets to look for files in your application's /node_modules directory and load it as above (recommended) or require cocooned in your application.js with:

//= require 'cocooned'

This compatibility with aging Rails assets pipelines will be removed in the next major release.

For all the following examples, we will consider modelisation of an administrable list with items. Here are the two ActiveRecord models : List and Item:

# == Schema Info
#
# Table name: lists
#
#  id           :integer(11)    not null, primary key
#  name         :string
class List < ApplicationRecord
  has_many :items, inverse_of: :list
  accepts_nested_attributes_for :items, reject_if: :all_blank, allow_destroy: true
end

# == Schema Info
#
# Table name: items
#
#  id           :integer(11)    not null, primary key
#  list_id      :integer(11)    not null
#  description  :text
#  done         :bool           not null, default(false)
class Item < ApplicationRecord
  belongs_to :list
end

We will build a form where we can dynamically add items to a list, remove or reorder them.

Rails natively supports nested forms but does not support adding or removing nested items.

<% # `app/views/lists/_form.html.erb` %>
<%= form_for @list do |form| %>
  <%= form.text_field :name %>
  
  <h3>Items</h3>
  <%= form.fields_for :items do |item_form| %>
    <%= item_form.label :description %>
    <%= item_form.text_field :description %>
    <%= item_form.check_box :done %>
  <% end %>
  
  <%= form.submit "Save" %>
<% end %>

To enable Cocooned on this form, we need to:

1. Move the nested form to a partial
2. Signal to Cocooned it should handle your form
3. Add a way to add a new item to the list
4. Add a way to remove an item from the collection

Let's do it.

Note: In this example, we will use Cocooned helpers named with a _link suffix. If you want to use buttons in your forms instead, the same helpers exist with a _button suffix.

Change your main form as follow:

<% # `app/views/lists/_form.html.erb` %>
<%= form_for @list do |form| %>
  <%= form.text_field :name %>
  
  <h3>Items</h3>
  <%= form.fields_for :items do |item_form|
-   <%= item_form.label :description %>
-   <%= item_form.text_field :description %>
-   <%= item_form.check_box :done %>
+   <%= render 'item_fields', f: item_form %>
  <% end %>
    
  <%= form.submit "Save" %>
<% end %>

And create a new file where items fields are defined:

<% # `app/views/lists/_item_fields.html.erb` %>
<%= f.label :description %>
<%= f.text_field :description %>
<%= f.check_box :done %>

Change your main form as follow:

<% # `app/views/lists/_form.html.erb` %>
<%= form_for @list do |form| %>
  <%= form.input :name %>
  
  <h3>Items</h3>
+ <%= cocooned_container do %>
    <%= form.fields_for :items do |item_form| %>
      <%= render 'item_fields', f: item_form %>
    <% end %>
+ <% end %>
  
  <%= form.submit "Save" %>
<% end %>

And your sub form as follow:

<% # `app/views/lists/_item_fields.html.erb` %>
+ <%= cocooned_item do %>
    <%= f.label :description %>
    <%= f.text_field :description %>
    <%= f.check_box :done %>
+ <% end %>

The cocooned_container and cocooned_item helpers will set for you the HTML attributes the JavaScript part of Cocooned expect to find to hook on. They will forward any option supported by ActionView's content_tag and accept a tag name as first argument if you don't want to use the default <div>.

Change your main form as follow:

<% # `app/views/lists/_form.html.erb` %>
<%= form_for @list do |form| %>
  <%= form.input :name %>
  
  <h3>Items</h3>
  <%= cocooned_container do %>
    <%= form.fields_for :items do |item_form| %>
      <%= render 'item_fields', f: item_form %>
    <% end %>
+   
+   <p><%= cocooned_add_item_link 'Add an item', form, :items %></p>
  <% end %>
  
  <%= form.submit "Save" %>
<% end %>

By default, new items will be inserted just before the immediate parent of the 'Add an item' link. You can have a look at the documentation of cocooned_add_item_link for more information about how to change that but we'll keep it simple for now.

Change your sub form as follow:

<% # `app/views/lists/_item_fields.html.erb` %>
<%= cocooned_item do %>
  <%= f.label :description %>
  <%= f.text_field :description %>
  <%= f.check_box :done %>
+ <%= cocooned_remove_item_link 'Remove', f %>
<% end %>

You're done!

To destroy nested models, Rails uses a virtual attribute called _destroy. When _destroy is set, the nested model will be deleted. If a record has previously been persisted, Rails generates and uses an additional id field.

When using Rails > 4.0 (or strong parameters), you need to explicitly add both :id and :_destroy to the list of permitted parameters in your controller.

In our example:

  def list_params
    params.require(:list).permit(:name, tasks_attributes: [:id, :description, :done, :_destroy])
  end

If you have a has_one association, then you (probably) need to set force_non_association_create: true on cocooned_add_item_link or the associated object will be destroyed every time the edit form is rendered (which is probably not what you expect).

See the original merge request for more details.

If you want to build complex forms with multiple levels of nesting, make sure you initialize Cocooned event handlers correctly for dynamically added child items or your form won't behave as you might expect.

Cocooned comes with two built-in plugins:

• Limit, to set a maximum limit of items the association can contain
• Reorderable, that will automatically update a position field in each of your sub forms when you add, remove or move an item.

The limit plugin requires you specify the maximum number of items allowed in the association. To do so, pass a :limit option to the cocooned_container helper:

<%= cocooned_container limit: 12 do %>
  <% # […] %>
<% end %>

Important: To use the reorderable plugin, your model must have a position numeric attribute you use to order collections (as in acts_as_list).

The reorderable plugin can be activated in two ways through the cocooned_container helper:

• With a boolean: cocooned_container reorderable: true
  Will use plugin's defaults (and start counting positions at 1)
• With a configuration hash: cocooned_container reorderable: { startAt: 0 }
  Will use given :startAt as base position

To be able to move items up and down in your form and for positions to be saved, you need to change your sub form as follow:

<% # `app/views/lists/_item_fields.html.erb` %>
<%= cocooned_item do %>
  <%= f.label :description %>
  <%= f.text_field :description %>
  <%= f.check_box :done %>
+ <%= f.hidden_field :position %>
+ <%= cocooned_move_item_up_link 'Up', f %>
+ <%= cocooned_move_item_down_link 'Down', f %>
  <%= cocooned_remove_item_link 'Remove', f %>
<% end %>

Remember to add :position as a permitted parameter in your controller.

Each helper provided by Cocooned with a name ending with _link has its _button equivalent, to generate a <button type="button" /> instead of a <a href="#" />:

• cocooned_add_item_link <=> cocooned_add_item_button (Documentation)
• cocooned_remove_item_link <=> cocooned_remove_item_button (Documentation)
• cocooned_move_item_up_link <=> cocooned_move_item_up_button (Documentation)
• cocooned_move_item_down_link <=> cocooned_move_item_down_button (Documentation)

While all _link helpers accept and will politely forward any option supported by ActionView's link_to, _button helpers will do the same with options supported by ActionView's button_tag.

The label of any action trigger can be given explicitly as helper's first argument or as a block, just as you can do with ActionView's link_to or button_to.

Additionally, Cocooned helpers will lookup I18n translations for a default label based on the action name (add, remove, up, down) and the association name. For add triggers, the association name used is the same as passed as argument. Other triggers extract the association name from form's #object_name.

You can declare default labels in your translation files with following keys:

• cocooned.{association}.{action} (Ex: cocooned.items.add)
• cocooned.defaults.{action}

If no translation is found, the default label will be the humanized action name.

For more documentation about the JavaScript bundled in the companion package, please refer to its own documentation.

Cocooned now uses exclusively data-attribute to hook JavaScript methods on but usual classes are still here and will stay so you can style your forms:

• .cocooned-container on a container
• .cocooned-item on an item
• .cocooned-add on an add trigger (link or button)
• .cocooned-remove on a remove trigger (link or button)
• .cocooned-move-up on a move up trigger (link or button)
• .cocooned-move-down on a move down trigger (link or button)

These migrations steps only highlight major changes. When upgrading from a previous version, always refer to the CHANGELOG for new features and breaking changes.

Cocooned 2.0 introduced the cocooned_container and cocooned_item helpers to respectively wrap the container where items will be added and each of the items.

If you used Cocooned ~1.0, you should modify your main forms as follow:

- <div data-cocooned-options="<%= {}.to_json %>">
+ <%= cocooned_container do %>
    <% # […] %>
+ <% end %>
- </div>

And your nested partials:

- <div class="cocooned-item">
+ <%= cocooned_item do %>
    <% # […] %>
+ <% end %>
- </div>

Support for the data-cocooned-options attribute to identify a container and the .cocooned-item class to identify an item is still here but it is not the recommended way to tag your containers and items anymore.

Compatibility with older markup will be dropped in the next major release.

Cocooned ~2.0 does not provide any styles anymore. If you used to require (with Sprockets) or import the cocooned stylesheets into your application, you need to remove it.

Empty files are included to not break your assets pipeline but will be removed in the next major release.

Cocoon uses a .nested_fields class to identify items in a nested form and nothing to identify containers new items will be added to.

If you used Cocoon, you should:

1. Modify your forms and sub forms to use the cocooned_container and cocooned_item helpers. (See above for examples)
2. Replace calls to link_to_add_association by cocooned_add_item_link
3. Replace calls to link_to_remove_association by cocooned_remove_item_link
4. Rename your I18n keys to use the cocooned namespace instead of cocoon

Compatibility with the original Cocoon API will be dropped in the next major release.