bootstrap_form 4.1.0 → 4.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d661bd91f892a0d10b09359e36a4846266f622e7fbc38430327bab3f51cd0e13
-  data.tar.gz: 4322fb71af8060d60a28268f00529d857eea8f5b09463953f21e32718ce64251
+  metadata.gz: 3eb9dd9edad01a3b8fc83d83506c4a9a19d70f849620dde77847baaaa0231b9a
+  data.tar.gz: 942e9b16f5ffe3873e49defc113255c61939e479621c25ed5846348b2bdfe304
 SHA512:
-  metadata.gz: 5e21b999c29774ec236fba107ed3d20476345cb60e5675f7aad7e56715ddc2307dc2ed397c51e44d3f35e62d2be1d8e14ffb455ff11d5b2f6ae80525306e0894
-  data.tar.gz: 176023ba2fe9ff4131996289508f63cd654011eddf23cb22c90afa739fcb49c369d7b68b1a533158f925faadcd76e40c23bf0b4dd7a4da96566ad59303967c34
+  metadata.gz: e61107ff84b13b61270438556d0320c94a1f395b5acdb9221122ba89078c7dca3c0d96b3f2db8bc5e3c7e0cdca4eb124f0bb5944fd47be31a9a217ad6a714716
+  data.tar.gz: 55b15e5a89aa152ad0c2ca05e1bfb6fc99c15f0e1b5235ad6a0d41df0429097e775d3c006ed59e0773e9b397d2c7332fb57334bc577a47331eebff0c7dff75b8

data/.gitignore

@@ -12,3 +12,21 @@ test/gemfiles/*.lock
 .ruby-version
 Vagrantfile
 .vagrant
+
+// For the demo app.
+
+# Ignore uploaded files in development.
+demo/storage/*
+!demo/storage/.keep
+
+demo/public/assets
+.byebug_history
+
+# Ignore master key for decrypting credentials and more.
+demo/config/master.key
+demo/public/packs
+demo/public/packs-test
+demo/node_modules
+demo/yarn-error.log
+demo/yarn-debug.log*
+demo/.yarn-integrity

data/.rubocop.yml

@@ -7,17 +7,18 @@ AllCops:
   Exclude:
     - "bin/*"
     - Capfile
+    - demo/bin/*
+    - "demo/bower_components/**/*"
     - demo/config/boot.rb
     - demo/config/environment.rb
     - demo/config/initializers/version.rb
     - demo/db/schema.rb
     - "demo/node_modules/**/*"
-    - "demo/bower_components/**/*"
+    - demo/Rakefile
     - "demo/tmp/**/*"
     - "demo/vendor/**/*"
     - Gemfile
     - Guardfile
-    - demo/Rakefile
     - Rakefile
 
 Layout/SpaceAroundEqualsInParameterDefault:

data/.travis.yml

@@ -16,10 +16,14 @@ script:
 
 matrix:
   include:
-    # Bleeding edge
+    # Bleeding edge Ruby
     - rvm: ruby-head
       gemfile: test/gemfiles/5.2.gemfile
 
+    # Next version of Rails
+    - rvm: 2.5.0
+      gemfile: test/gemfiles/6.0.gemfile
+
     # Running one job to execute DANGER bot and linting
     - rvm: 2.5.0
       gemfile: test/gemfiles/5.2.gemfile
@@ -30,3 +34,5 @@ matrix:
 
   allow_failures:
     - rvm: ruby-head
+    - rvm: 2.5.0
+      gemfile: test/gemfiles/6.0.gemfile

data/CHANGELOG.md

@@ -12,6 +12,19 @@
 
 * Your contribution here!
 
+## [4.2.0][] (2019-03-08)
+
+### New features
+
+* [#508] Support `rich_text_area` AKA the Trix editor on Rails 6+.
+* [#518] Move all inputs to separate, more maintainable files.
+* [#514](https://github.com/bootstrap-ruby/bootstrap_form/pull/514): Add support for BS 4.2 switches - [@simmerz](https://github.com/simmerz)
+
+### Bugfixes
+
+* [#522](https://github.com/bootstrap-ruby/bootstrap_form/pull/522): Clean up rubocop offences - [@simmerz](https://github.com/simmerz)
+* [#524](https://github.com/bootstrap-ruby/bootstrap_form/pull/524): Fix non-inline layout rendering without help text - [@simmerz](https://github.com/simmerz)
+
 ## [4.1.0][] (2019-01-19)
 
 ### New features
@@ -255,7 +268,8 @@ Features:
   - Added support for bootstrap_form_tag (@baldwindavid)
 
 
-[Pending Release]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v4.1.0...HEAD
+[Pending Release]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v4.2.0...HEAD
+[4.2.0]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v4.1.0...v4.2.0
 [4.1.0]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v4.0.0...v4.1.0
 [4.0.0]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v4.0.0.alpha1...v4.0.0
 [4.0.0.alpha1]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v2.7.0...v4.0.0.alpha1

data/CONTRIBUTING.md

@@ -84,3 +84,14 @@ We are an entirely volunteer project. Sometimes it's hard for people to find the
 ---
 
 Thanks to all the great contributors over the years: https://github.com/bootstrap-ruby/bootstrap_form/graphs/contributors
+
+## Troubleshooting
+### Models and Database Tables
+`bootstrap_form` needs a few models and tables to support testing. It appears that the necessary tables were created via the `demo/db/schema.rb` file. To support `rich_text_area`, Rails 6 creates some migrations. These migrations had to be run in the existing database (not an empty one) to create a new `schema.rb` that creates the `bootstrap_form` test tables, and the tables needed by Rails 6. The `schema.rb` file was checked in to GitHub, but the migrations were not.
+
+In the future, any new Rails functionality that creates tables would likely have to be prepared the same way:
+```
+cd demo
+rails db:setup # create the databases from `schema.rb`
+rails db:migrate # add the new tables and create a new `schema.rb`
+```

data/Dangerfile

@@ -30,11 +30,11 @@ end
 # ------------------------------------------------------------------------------
 if !has_changelog_changes && has_lib_changes
   markdown <<-MARKDOWN
-Here's an example of a CHANGELOG.md entry (place it immediately under the `* Your contribution here!` line):
+  Here's an example of a CHANGELOG.md entry (place it immediately under the `* Your contribution here!` line):
 
-```markdown
-* [##{pr_number}](#{pr_url}): #{github.pr_title} - [@#{github.pr_author}](https://github.com/#{github.pr_author}).
-```
+  ```markdown
+  * [##{pr_number}](#{pr_url}): #{github.pr_title} - [@#{github.pr_author}](https://github.com/#{github.pr_author}).
+  ```
   MARKDOWN
   warn("Please update CHANGELOG.md with a description of your changes. "\
        "If this PR is not a user-facing change (e.g. just refactoring), "\

data/Gemfile

@@ -3,12 +3,15 @@ source "http://rubygems.org"
 gemspec
 
 # Uncomment and change rails version for testing purposes
-# gem "rails", "~> 5.2.0.beta2"
+gem "rails", "~> 5.2.0"
+# gem "rails", "~> 6.0.0.beta1"
 
 group :development do
   gem "chandler", ">= 0.7.0"
   gem "htmlbeautifier"
   gem "rubocop", require: false
+  gem "sass-rails"
+  gem 'webpacker', '>= 4.0.0.rc.3'
 end
 
 group :test do
@@ -18,6 +21,8 @@ group :test do
   gem "diffy"
   gem "equivalent-xml"
   gem "mocha"
-  gem "sqlite3"
+  # sqlite3 1.4.0 breaks the test suite.
+  # https://github.com/rails/rails/pull/35154
+  gem "sqlite3", "~> 1.3.6"
   gem "timecop", "~> 0.7.1"
 end

data/OLD-README.md

@@ -0,0 +1,795 @@
+⚠️ **This documentation is for the master branch, which targets Bootstrap v4.** If you are using Bootstrap v3, refer to the stable [legacy-2.7](https://github.com/bootstrap-ruby/bootstrap_form/tree/legacy-2.7) branch.
+
+Try our new [README](/README.md)
+
+---
+
+# bootstrap_form
+
+[![Build Status](https://travis-ci.org/bootstrap-ruby/bootstrap_form.svg?branch=master)](https://travis-ci.org/bootstrap-ruby/bootstrap_form)
+[![Gem Version](https://badge.fury.io/rb/bootstrap_form.svg)](https://rubygems.org/gems/bootstrap_form)
+
+**bootstrap_form** is a Rails form builder that makes it super easy to integrate
+Bootstrap v4-style forms into your Rails application.
+
+## Requirements
+
+* Ruby 2.2.2+
+* Rails 5.0+ (Rails 5.1+ for `bootstrap_form_with`)
+* Bootstrap 4.0.0+
+
+## Installation
+
+Add it to your Gemfile:
+
+```ruby
+gem "bootstrap_form", ">= 4.1.0"
+```
+
+Then:
+
+`bundle`
+
+Then require the CSS in your `application.css` file:
+
+```css
+/*
+ *= require rails_bootstrap_forms
+ */
+```
+
+## Usage
+
+To get started, just use the `bootstrap_form_for` helper. Here's an example:
+
+```erb
+<%= bootstrap_form_for(@user) do |f| %>
+  <%= f.email_field :email %>
+  <%= f.password_field :password %>
+  <%= f.check_box :remember_me %>
+  <%= f.submit "Log In" %>
+<% end %>
+```
+
+This generates the following HTML:
+
+```html
+<form accept-charset="UTF-8" action="/users" class="new_user" id="new_user" method="post">
+  <div class="form-group">
+    <label for="user_email">Email</label>
+    <input class="form-control" id="user_email" name="user[email]" type="email">
+  </div>
+  <div class="form-group">
+    <label for="user_password">Password</label>
+    <input class="form-control" id="user_password" name="user[password]" type="password">
+  </div>
+  <div class="form-check">
+    <input name="user[remember_me]" type="hidden" value="0">
+    <input class="form-check-input" id="user_remember_me" name="user[remember_me]" type="checkbox" value="1">
+    <label class="form-check-label" for="user_remember_me">Remember me</label>
+  </div>
+  <input class="btn btn-secondary" name="commit" type="submit" value="Log In">
+</form>
+```
+
+### bootstrap_form_tag
+
+If your form is not backed by a model, use the `bootstrap_form_tag`. Usage of this helper is the same as `bootstrap_form_for`, except no model object is passed in as the first argument. Here's an example:
+
+```erb
+<%= bootstrap_form_tag url: '/subscribe' do |f| %>
+  <%= f.email_field :email, value: 'name@example.com' %>
+  <%= f.submit %>
+<% end %>
+```
+
+### `bootstrap_form_with` (Rails 5.1+)
+
+Note that `form_with` in Rails 5.1 does not add IDs to form elements and labels by default, which are both important to Bootstrap markup. This behavior is corrected in Rails 5.2.
+
+To get started, just use the `bootstrap_form_with` helper in place of `form_with`. Here's an example:
+
+```erb
+<%= bootstrap_form_with(model: @user, local: true) do |f| %>
+  <%= f.email_field :email %>
+  <%= f.password_field :password %>
+  <%= f.check_box :remember_me %>
+  <%= f.submit "Log In" %>
+<% end %>
+```
+
+This generates:
+
+```html
+<form role="form" action="/users" accept-charset="UTF-8" method="post">
+  <input name="utf8" type="hidden" value="&#x2713;" />
+  <div class="form-group">
+    <label class="required" for="user_email">Email</label>
+    <input class="form-control" type="email" value="steve@example.com" name="user[email]" />
+  </div>
+  <div class="form-group">
+    <label for="user_password">Password</label>
+    <input class="form-control" type="password" name="user[password]" />
+    <small class="form-text text-muted">A good password should be at least six characters long</small>
+  </div>
+  <div class="form-check">
+    <input name="user[remember_me]" type="hidden" value="0">
+    <input class="form-check-input" id="user_remember_me" name="user[remember_me]" type="checkbox" value="1">
+    <label class="form-check-label" for="user_remember_me">Remember me</label>
+  </div>
+  <input type="submit" name="commit" value="Log In" class="btn btn-secondary" data-disable-with="Log In" />
+</form>
+```
+
+`bootstrap_form_with` supports both the `model:` and `url:` use cases
+in `form_with`.
+
+`form_with` has some important differences compared to `form_for` and `form_tag`, and these differences apply to `bootstrap_form_with`. A good summary of the differences can be found at: https://m.patrikonrails.com/rails-5-1s-form-with-vs-old-form-helpers-3a5f72a8c78a, or in the [Rails documentation](api.rubyonrails.org).
+
+### Future Compatibility
+
+The Rails team has [suggested](https://github.com/rails/rails/issues/25197) that `form_for` and `form_tag` may be deprecated and then removed in future versions of Rails. `bootstrap_form` will continue to support `bootstrap_form_for` and `bootstrap_form_tag` as long as Rails supports `form_for` and `form_tag`.
+
+## Form Helpers
+
+This gem wraps the following Rails form helpers:
+
+* check_box
+* collection_check_boxes
+* collection_select
+* color_field
+* date_field
+* date_select
+* datetime_field
+* datetime_local_field
+* datetime_select
+* email_field
+* file_field
+* grouped_collection_select
+* hidden_field (not wrapped, but supported)
+* month_field
+* number_field
+* password_field
+* phone_field
+* radio_button
+* collection_radio_buttons
+* range_field
+* rich_text_area (Rails 6+)
+* search_field
+* select
+* telephone_field
+* text_area
+* text_field
+* time_field
+* time_select
+* time_zone_select
+* url_field
+* week_field
+* submit
+* button
+
+These helpers accept the same options as the standard Rails form helpers, with
+a few extra options:
+
+### Labels
+
+Use the `label` option if you want to specify the field's label text:
+
+```erb
+<%= f.password_field :password_confirmation, label: "Confirm Password" %>
+```
+
+To hide a label, use the `hide_label: true` option. This adds the `sr-only`
+class, which keeps your labels accessible to those using screen readers.
+
+```erb
+<%= f.text_area :comment, hide_label: true, placeholder: "Leave a comment..." %>
+```
+
+To add custom classes to the field's label:
+
+```erb
+<%= f.text_field :email, label_class: "custom-class" %>
+```
+
+Or you can add the label as input placeholder instead (this automatically hides the label):
+
+```erb
+<%= f.text_field :email, label_as_placeholder: true %>
+```
+
+#### Required Fields
+
+A label that is associated with a required field is automatically annotated with
+a `required` CSS class. You are free to add any appropriate CSS to style
+required fields as desired.  One example would be to automatically add an
+asterisk to the end of the label:
+
+```css
+label.required:after {
+  content:" *";
+}
+```
+
+The label `required` class is determined based on the definition of a presence
+validator with the associated model attribute. Presently this is one of:
+ActiveRecord::Validations::PresenceValidator or
+ActiveModel::Validations::PresenceValidator.
+
+In cases where this behavior is undesirable, use the `required` option to force the class to be present or absent:
+
+```erb
+<%= f.password_field :login, label: "New Username", required: true %>
+<%= f.password_field :password, label: "New Password", required: false %>
+```
+
+### Input Elements / Controls
+
+To specify the class of the generated input tag, use the `control_class` option:
+
+```erb
+<%= f.text_field :email, control_class: "custom-class" %>
+```
+
+### Help Text
+
+To add help text, use the `help` option:
+
+```erb
+<%= f.password_field :password, help: "Must be at least 6 characters long" %>
+```
+
+This gem is also aware of help messages in locale translation files (i18n):
+
+```yml
+en:
+  activerecord:
+    help:
+      user:
+        password: "A good password should be at least six characters long"
+```
+
+Help translations containing HTML should follow the convention of appending `_html` to the name:
+
+```yml
+en:
+  activerecord:
+    help:
+      user:
+        password_html: "A <strong>good</strong> password should be at least six characters long"
+```
+
+If your model name has multiple words (like `SuperUser`), the key on the
+translation file should be underscored (`super_user`).
+
+You can override help translations for a particular field by passing the `help`
+option or turn them off completely by passing `help: false`.
+
+### Prepending and Appending Inputs
+
+You can pass `prepend` and/or `append` options to input fields:
+
+```erb
+<%= f.text_field :price, prepend: "$", append: ".00" %>
+```
+
+You can also prepend and append buttons. Note: The buttons must contain the
+`btn` class to generate the correct markup.
+
+```erb
+<%= f.text_field :search, append: link_to("Go", "#", class: "btn btn-secondary") %>
+```
+
+To add a class to the input group wrapper, use the `:input_group_class` option.
+
+```erb
+<%= f.email_field :email, append: f.primary('Subscribe'), input_group_class: 'input-group-lg' %>
+```
+
+### Additional Form Group Attributes
+
+If you want to add an additional css class or any other attribute to the form group div, you can use
+the `wrapper: { class: 'additional-class', data: { foo: 'bar' } }` option.
+
+```erb
+<%= f.text_field :name, wrapper: { class: 'has-warning', data: { foo: 'bar' } } %>
+```
+
+Which produces the following output:
+
+```erb
+<div class="form-group has-warning" data-foo="bar">
+  <label class="form-control-label" for="user_name">Id</label>
+  <input class="form-control" id="user_name" name="user[name]" type="text">
+</div>
+```
+
+You still can use `wrapper_class` option to set only a css class. This is just a short form of `wrapper: { class: 'additional-class' }`.
+
+### Suppressing the Form Group Altogether
+
+You may have want to define your own form group div around a field. To do so, add the option `wrapper: false` to the input field. For example:
+
+```
+f.form_group :user do
+  f.email_field :email, wrapper: false
+end
+```
+
+Note that Bootstrap relies on the form group div to correctly format most fields, so if you use the `wrapper: false` option, you should provide your own form group div around the input field. You can write your own HTML, or use the `form_group` helper.
+
+### Selects
+
+Our select helper accepts the same arguments as the [default Rails helper](http://api.rubyonrails.org/classes/ActionView/Helpers/FormOptionsHelper.html#method-i-select). Here's an example of how you pass both options and html_options hashes:
+
+```erb
+<%= f.select :product, [["Apple", 1], ["Grape", 2]], { label: "Choose your favorite fruit:", wrapper: { class: 'has-warning', data: { foo: 'bar' } } }, { class: "selectpicker" } %>
+```
+
+### Checkboxes and Radios
+
+Checkboxes and radios should be placed inside of a `form_group` to render
+properly. The following example ensures that the entire form group will display
+an error if an associated validations fails:
+
+```erb
+<%= f.form_group :skill_level, label: { text: "Skill" }, help: "Optional Help Text" do %>
+  <%= f.radio_button :skill_level, 0, label: "Novice", checked: true %>
+  <%= f.radio_button :skill_level, 1, label: "Intermediate" %>
+  <%= f.radio_button :skill_level, 2, label: "Advanced" %>
+<% end %>
+
+<%= f.form_group :terms do %>
+  <%= f.check_box :terms, label: "I agree to the Terms of Service" %>
+<% end %>
+```
+
+You can also create a checkbox using a block:
+
+```erb
+<%= f.form_group :terms, label: { text: "Optional Label" } do %>
+  <%= f.check_box :terms do %>
+    You need to check this box to accept our terms of service and privacy policy
+  <% end %>
+<% end %>
+```
+
+To display checkboxes and radios inline, pass the `inline: true` option:
+
+```erb
+<%= f.form_group :skill_level, label: { text: "Skill" } do %>
+  <%= f.radio_button :skill_level, 0, label: "Novice", inline: true %>
+  <%= f.radio_button :skill_level, 1, label: "Intermediate", inline: true %>
+  <%= f.radio_button :skill_level, 2, label: "Advanced", inline: true %>
+<% end %>
+```
+
+Check boxes and radio buttons are wrapped in a `div.form-check`. You can add classes to this `div` with the `:wrapper_class` option:
+
+```erb
+<%= f.radio_button :skill_level, 0, label: "Novice", inline: true, wrapper_class: "w-auto" %>
+```
+#### Switches
+
+To render checkboxes as switches with Bootstrap 4.2+, add the proper wrapper class:
+
+```erb
+<%= f.check_box :remember_me, custom: true, wrapper_class: 'custom-switch' %>
+```
+
+#### Collections
+
+`bootstrap_form` also provides helpers that automatically create the
+`form_group` and the `radio_button`s or `check_box`es for you:
+
+```erb
+<%= f.collection_radio_buttons :skill_level, Skill.all, :id, :name %>
+<%= f.collection_check_boxes :skills, Skill.all, :id, :name %>
+```
+
+Collection methods accept these options:
+* `:label`: Customize the `form_group`'s label
+* `:hide_label`: Pass true to hide the `form_group`'s label
+* `:help`: Add a help span to the `form_group`
+* Other options will be forwarded to the `radio_button`/`check_box` method
+
+### Static Controls
+
+You can create a static control like this:
+
+```erb
+<%= f.static_control :email %>
+```
+
+Here's the output for a horizontal layout:
+
+```html
+<div class="form-group">
+  <label class="col-sm-2 form-control-label" for="user_email">Email</label>
+  <div class="col-sm-10">
+    <input class="form-control-plaintext" id="user_email" name="user[email]" readonly="readonly" type="text" value="test@email.com"/>
+  </div>
+</div>
+```
+
+You can also create a static control that isn't based on a model attribute:
+
+```erb
+<%= f.static_control label: "Custom Static Control" value: "Content Here" %>
+```
+Prior to version 4 of `bootstrap_form`, you could pass a block to the `static_control` method.
+The value of the block would be used for the content of the static "control".
+Bootstrap 4 actually creates and styles a disabled input field for static controls, so the value of the control has to be specified by the `value:` option.
+Passing a block to `static_control` no longer has any effect.
+
+### Date Helpers
+
+The multiple selects that the date and time helpers (`date_select`,
+`time_select`, `datetime_select`) generate are wrapped inside a
+`div.rails-bootstrap-forms-[date|time|datetime]-select` tag. This is because
+Bootstrap automatically styles our controls as `block`s. This wrapper fixes
+this defining these selects as `inline-block` and a width of `auto`.
+
+### Submit Buttons
+
+The `btn btn-secondary` CSS classes are automatically added to your submit
+buttons.
+
+```erb
+<%= f.submit %>
+```
+
+You can also use the `primary` helper, which adds `btn btn-primary` to your
+submit button:
+
+```erb
+<%= f.primary "Optional Label" %>
+```
+
+You can specify your own classes like this:
+
+```erb
+<%= f.submit "Log In", class: "btn btn-success" %>
+```
+
+If the `primary` helper receives a `render_as_button: true` option or a block,
+it will be rendered as an HTML button, instead of an input tag. This allows you
+to specify HTML content and styling for your buttons (such as adding
+illustrative icons to them). For example, the following statements
+
+```erb
+<%= f.primary "Save changes <span class='fa fa-save'></span>".html_safe, render_as_button: true %>
+
+<%= f.primary do
+      concat 'Save changes '
+      concat content_tag(:span, nil, class: 'fa fa-save')
+    end %>
+```
+
+are equivalent, and each of them both be rendered as
+
+```html
+<button name="button" type="submit" class="btn btn-primary">Save changes <span class="fa fa-save"></span></button>
+```
+
+If you wish to add additional CSS classes to your button, while keeping the
+default ones, you can use the `extra_class` option. This is particularly useful
+for adding extra details to buttons (without forcing you to repeat the
+Bootstrap classes), or for element targeting via CSS classes.
+Be aware, however, that using the `class` option will discard any extra classes
+you add. As an example, the following button declarations
+
+```erb
+<%= f.primary "My Nice Button", extra_class: 'my-button' %>
+
+<%= f.primary "My Button", class: 'my-button' %>
+```
+
+will be rendered as
+
+```html
+<input type="submit" value="My Nice Button" class="btn btn-primary my-button" />
+
+<input type="submit" value="My Button" class="my-button" />
+```
+
+(some unimportant HTML attributes have been removed for simplicity)
+
+### Rich Text Areas AKA Trix Editor
+If you're using Rails 6, and `bootstrap_form` from the master branch on GitHub,
+`bootstrap_form` supports the `rich_text_area` helper.
+
+```
+<%= f.rich_text_area(:life_story) %>
+```
+will be rendered as:
+```
+<div class="form-group">
+  <label for="user_life_story">Life story</label>
+  <input type="hidden" name="user[life_story]" id="user_life_story_trix_input_user"/>
+  <trix-editor id="user_life_story" data-blob-url-template="http://test.host/rails/active_storage/blobs/:signed_id/:filename" data-direct-upload-url="http://test.host/rails/active_storage/direct_uploads" input="user_life_story_trix_input_user" class="trix-content form-control"/>
+  </trix-editor>
+</div>
+```
+
+To use `bootstrap_form` from the master branch of GitHub, change the `bootstrap_form` line in your `Gemfile` to:
+```
+gem "bootstrap_form", git: "https://github.com/bootstrap-ruby/bootstrap_form"
+```
+
+Support for `rich_text_area` is highly experimental at this time.
+Please submit bugs to the [issue tracker](https://github.com/bootstrap-ruby/bootstrap_form/issues).
+
+### Accessing Rails Form Helpers
+
+If you want to use the original Rails form helpers for a particular field,
+append `_without_bootstrap` to the helper:
+
+```erb
+<%= f.text_field_without_bootstrap :email %>
+```
+
+## Form Styles
+
+By default, your forms will stack labels on top of controls and your controls
+will grow to 100% of the available width.
+
+### Inline Forms
+
+To use an inline-layout form, use the `layout: :inline` option. To hide labels,
+use the `hide_label: true` option, which keeps your labels accessible to those
+using screen readers.
+
+```erb
+<%= bootstrap_form_for(@user, layout: :inline) do |f| %>
+  <%= f.email_field :email, hide_label: true %>
+  <%= f.password_field :password, hide_label: true %>
+  <%= f.check_box :remember_me %>
+  <%= f.submit %>
+<% end %>
+```
+
+To skip label rendering at all, use `skip_label: true` option.
+
+```erb
+<%= f.password_field :password, skip_label: true %>
+```
+
+### Horizontal Forms
+
+To use a horizontal-layout form with labels to the left of the control, use the
+`layout: :horizontal` option. You should specify both `label_col` and
+`control_col` css classes as well (they default to `col-sm-2` and `col-sm-10`).
+
+In the example below, the checkbox and submit button have been wrapped in a
+`form_group` to keep them properly aligned.
+
+```erb
+<%= bootstrap_form_for(@user, layout: :horizontal, label_col: "col-sm-2", control_col: "col-sm-10") do |f| %>
+  <%= f.email_field :email %>
+  <%= f.password_field :password %>
+  <%= f.form_group do %>
+    <%= f.check_box :remember_me %>
+  <% end %>
+  <%= f.form_group do %>
+    <%= f.submit %>
+  <% end %>
+<% end %>
+```
+
+The `label_col` and `control_col` css classes can also be changed per control:
+
+```erb
+<%= bootstrap_form_for(@user, layout: :horizontal) do |f| %>
+  <%= f.email_field :email %>
+  <%= f.text_field :age, control_col: "col-sm-3" %>
+  <%= f.form_group do %>
+    <%= f.submit %>
+  <% end %>
+<% end %>
+```
+
+or default value can be changed in initializer:
+
+```erb
+# config/initializers/bootstrap_form.rb
+module BootstrapForm
+  class FormBuilder
+    def default_label_col
+      'col-sm-4'
+    end
+    def default_control_col
+      'col-sm-8'
+    end
+  end
+end
+```
+
+Control col wrapper class can be modified with `add_control_col_class`. This option will preserve column definition:
+
+```erb
+<%= bootstrap_form_for(@user, layout: :horizontal) do |f| %>
+  <%= f.email_field :email %>
+  <%= f.text_field :age, add_control_col_class: "additional-control-col-class" %>
+  <%= f.form_group do %>
+    <%= f.submit %>
+  <% end %>
+<% end %>
+```
+
+### Custom Field Layout
+
+The form-level `layout` can be overridden per field, unless the form-level layout was `inline`:
+
+```erb
+<%= bootstrap_form_for(@user, layout: :horizontal) do |f| %>
+  <%= f.email_field :email %>
+  <%= f.text_field :feet, layout: :default %>
+  <%= f.text_field :inches, layout: :default %>
+  <%= f.form_group do %>
+    <%= f.submit %>
+  <% end %>
+<% end %>
+```
+
+A form-level `layout: :inline` can't be overridden because of the way Bootstrap 4 implements in-line layouts. One possible work-around is to leave the form-level layout as default, and specify the individual fields as `layout: :inline`, except for the fields(s) that should be other than in-line.
+
+### Custom Form Element Styles
+
+The `custom` option can be used to replace the browser default styles for check boxes and radio buttons with dedicated Bootstrap styled form elements. Here's an example:
+
+```erb
+<%= bootstrap_form_for(@user) do |f| %>
+  <%= f.email_field :email %>
+  <%= f.password_field :password %>
+  <%= f.check_box :remember_me, custom: true %>
+  <%= f.submit "Log In" %>
+<% end %>
+```
+
+## Validation and Errors
+
+### Inline Errors
+
+By default, fields that have validation errors will be outlined in red and the
+error will be displayed below the field. Rails normally wraps the fields in a
+div (field_with_errors), but this behavior is suppressed. Here's an example:
+
+```html
+<div class="form-group">
+  <label class="form-control-label" for="user_email">Email</label>
+  <input class="form-control is-invalid" id="user_email" name="user[email]" type="email" value="">
+  <small class="invalid-feedback">can't be blank</small>
+</div>
+```
+
+You can turn off inline errors for the entire form like this:
+
+```erb
+<%= bootstrap_form_for(@user, inline_errors: false) do |f| %>
+  ...
+<% end %>
+```
+
+### Label Errors
+
+You can also display validation errors in the field's label; just turn
+on the `:label_errors` option. Here's an example:
+
+```
+<%= bootstrap_form_for(@user, label_errors: true) do |f| %>
+  ...
+<% end %>
+```
+
+By default, turning on `:label_errors` will also turn off
+`:inline_errors`. If you want both turned on, you can do that too:
+
+```
+<%= bootstrap_form_for(@user, label_errors: true, inline_errors: true) do |f| %>
+  ...
+<% end %>
+```
+
+### Alert Messages
+
+To display an error message with an error summary, you can use the
+`alert_message` helper. This won't output anything unless a model validation
+has failed.
+
+```erb
+<%= f.alert_message "Please fix the errors below." %>
+```
+
+Which outputs:
+
+```html
+<div class="alert alert-danger">
+  <p>Please fix the errors below.</p>
+  <ul class="rails-bootstrap-forms-error-summary">
+    <li>Email can't be blank</li>
+  </ul>
+</div>
+```
+
+You can turn off the error summary like this:
+
+```erb
+<%= f.alert_message "Please fix the errors below.", error_summary: false %>
+```
+
+To output a simple unordered list of errors, use the `error_summary` helper.
+
+```erb
+<%= f.error_summary %>
+```
+
+Which outputs:
+
+```html
+<ul class="rails-bootstrap-forms-error-summary">
+  <li>Email can't be blank</li>
+</ul>
+```
+
+### Errors On
+
+If you want to display a custom inline error for a specific attribute not
+represented by a form field, use the `errors_on` helper.
+
+```erb
+<%= f.errors_on :tasks %>
+```
+
+Which outputs:
+
+```html
+<div class="alert alert-danger">Tasks can't be blank.</div>
+```
+
+You can hide the attribute name like this:
+
+```erb
+<%= f.errors_on :tasks, hide_attribute_name: true %>
+```
+
+Which outputs:
+
+```html
+<div class="alert alert-danger">can't be blank.</div>
+```
+
+## Internationalization
+
+bootstrap_form follows standard rails conventions so it's i18n-ready. See more
+here: http://guides.rubyonrails.org/i18n.html#translations-for-active-record-models
+
+## Other Tips and Edge Cases
+By their very nature, forms are extremely diverse. It would be extremely difficult to provide a gem that could handle every need. Here are some tips for handling edge cases.
+
+### Empty But Visible Labels
+Some third party plug-ins require an empty but visible label on an input control. The `hide_label` option generates a label that won't appear on the screen, but it's considered invisible and therefore doesn't work with such a plug-in. An empty label (e.g. `""`) causes the underlying Rails helper to generate a label based on the field's attribute's name.
+
+The solution is to use a zero-width character for the label, or some other "empty" HTML. For example:
+```
+label: "&#8203;".html_safe
+```
+or
+```
+label: "<span></span>".html_safe
+```
+
+## Code Triage page
+
+http://www.codetriage.com/potenza/bootstrap_form
+
+## Contributing
+
+We welcome contributions.
+If you're considering contributing to bootstrap_form,
+please review the [Contributing](/CONTRIBUTING.md)
+document first.
+
+## License
+
+MIT License. Copyright 2012-2018 Stephen Potenza (https://github.com/potenza)