bootstrap_form_legacy 4.0.1.dev

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 17d418df87737df9566ebde69bc92c34066c8e46
+  data.tar.gz: e46f31797c39ab157fee4aca2a67b012da4548c9
+SHA512:
+  metadata.gz: '0786ef134cb6f9a67e565498ecefe42f56fc7b0b83659ace6daa2006e745ec140ee83de1713b87d1b806174130d7be1e3f85044e9b5d679ccaa0bdb88afdcf1e'
+  data.tar.gz: 770da09a7d3ebf397dcd85021fe20c8c04fa32ab4ffeefe70fead630aba093dcf70f1b30f0389f7f078b9945a0036092a48f8c7bfa43fec570893b66c66f30c7

data/.gitignore

@@ -0,0 +1,14 @@
+.bundle/
+log/*.log
+pkg/
+demo/db/*.sqlite3
+demo/log/*.log
+demo/tmp/
+*.gem
+.rbenv-gemsets
+*.swp
+Gemfile.lock
+test/gemfiles/*.lock
+.ruby-version
+Vagrantfile
+.vagrant

data/.travis.yml

@@ -0,0 +1,29 @@
+language: ruby
+rvm:
+  - 2.2.9
+  - 2.3.6
+  - 2.4.3
+  - 2.5.0
+gemfile:
+  - test/gemfiles/5.0.gemfile
+  - test/gemfiles/5.1.gemfile
+  - test/gemfiles/5.2.gemfile
+before_install:
+  - gem update --system
+  - gem install bundler --no-document
+
+matrix:
+  include:
+    # Bleeding edge
+    - rvm: ruby-head
+      gemfile: test/gemfiles/5.2.gemfile
+
+    # Running one job to execute DANGER bot
+    - rvm: 2.5.0
+      gemfile: test/gemfiles/5.2.gemfile
+      script:
+        - gem install danger
+        - danger
+
+  allow_failures:
+    - rvm: ruby-head

data/CHANGELOG.md

@@ -0,0 +1,207 @@
+## [Pending Release][]
+
+🚨 **This release adds support for Bootstrap v4 and drops support for Bootstrap v3.** 🚨
+
+If your app uses Bootstrap v3, you should continue using bootstrap_form 2.7.x instead.
+
+Bootstrap v3 and v4 are very different, and thus bootstrap_form now produces different markup in order to target v4. The changes are too many to list here; you can refer to Bootstrap's [Migrating to v4](https://getbootstrap.com/docs/4.0/migration/) page for a detailed explanation.
+
+In addition to these necessary markup changes, the bootstrap_form API itself has the following important changes in this release.
+
+### Breaking changes
+
+* Rails 4.x is no longer supported
+* Ruby 2.2 or newer is required
+* Built-in support for the `nested_form` gem has been completely removed
+* The `icon` option is no longer supported (Bootstrap v4 does not include icons)
+* The deprecated Rails methods `check_boxes_collection` and `radio_buttons_collection` have been removed
+* `hide_label: true` and `skip_label: true` on individual check boxes and radio buttons apply Bootstrap 4 markup. This means the appearance of a page may change if you're upgrading from the Bootstrap 3 version of `bootstrap_form`, and you used `check_box` or `radio_button` with either of those options
+* `static_control` will no longer properly show error messages. This is the result of bootstrap changes.
+* `static_control` will also no longer accept a block, use the `value` option instead.
+* Your contribution here!
+* [#456](https://github.com/bootstrap-ruby/bootstrap_form/pull/456): Fix label `for` attribute when passing non-english characters using `collection_check_boxes` - [@ug0](https://github.com/ug0).
+
+### New features
+
+* Support for Rails 5.1 `form_with` - [@lcreid](https://github.com/lcreid).
+* Support Bootstrap v4's [Custom Checkboxes and Radios](https://getbootstrap.com/docs/4.0/components/forms/#checkboxes-and-radios-1) with a new `custom: true` option
+* Allow HTML in help translations by using the `_html` suffix on the key - [@unikitty37](https://github.com/unikitty37)
+* [#408](https://github.com/bootstrap-ruby/bootstrap_form/pull/408): Add option[:id] on static control #245 - [@duleorlovic](https://github.com/duleorlovic).
+* [#455](https://github.com/bootstrap-ruby/bootstrap_form/pull/455): Support for i18n `:html` subkeys in help text - [@jsaraiva](https://github.com/jsaraiva).
+* Your contribution here!
+
+### Bugfixes
+
+* [#357](https://github.com/bootstrap-ruby/bootstrap_form/pull/357) if provided,
+  use html option `id` to specify `for` attribute on label
+  [@duleorlovic](https://github.com/duleorlovic)
+* Your contribution here!
+
+
+## [2.7.0][] (2017-04-21)
+
+Features:
+  * [#325](https://github.com/bootstrap-ruby/bootstrap_form/pull/325): Support :prepend and :append for the `select` helper - [@donv](https://github.com/donv).
+
+## [2.6.0][] (2017-02-03)
+
+Bugfixes:
+  - Fix ambiguous first argument warning (#311, @mikenicklas)
+
+Features:
+  - Add a FormBuilder#custom_control helper [#289](https://github.com/bootstrap-ruby/bootstrap_form/pull/289)
+
+## [2.5.3][] (2016-12-23)
+
+There are no user-facing changes with this release. Behind the scenes, the tests have been greatly improved. The project is now tested against and compatible with the following Rails versions 4.0, 4.1, 4.2 and 5.0 (#278).
+
+## [2.5.2][] (2016-10-08)
+
+Bugfixes:
+  - Allow objects without `model_name`s to act as form objects (#295, @laserlemon)
+  - Fix offset for submit for horizontal forms when using non-sm column breakers for label column (#293, @oteyatosys)
+
+## [2.5.1][] (2016-09-23)
+
+Bugfixes:
+  - Fix getting help text for elements when using anonymous models (see [issue 282](https://github.com/bootstrap-ruby/bootstrap_form/issues/282))
+
+## [2.5.0][] (2016-08-12)
+
+Bugfixes:
+
+  - Sanitize <label> name (IE `for` attribute) in same manner that Rails sanitizes
+    the <input> `id` attribute to fix a11y issue with `for` and `id` mismatch
+  - Fix loading of ActionView helpers in combination with RSpec and `rails-controller-testing`. (see [rails-controller-testing/issues#24](https://github.com/rails/rails-controller-testing/issues/24))
+
+Features:
+
+  - Add support for input-group-sm and input-group-lg in prepend/append (#226, @rusanu)
+  - Added option to prevent the 'required' CSS class on labels (#205, @LucasAU)
+
+## [2.4.0][] (2016-07-04)
+
+This version is ready to use with Rails 5.0.0!
+
+Bugfixes:
+
+  - Minor README corrections (#184, @msmithstubbs)
+  - Fix `alias_method_chain` deprecation warnings when using Rails 5
+  - Allow `form_group` to work with frozen string options
+
+Features:
+
+  - Allow primary button classes to be overridden (#183, @tanimichi)
+  - Allow to pass a block to select helper in Rails >= 4.1.0 (#229, @doits)
+
+## 2.3.0 (2015-02-17)
+
+Bugfixes:
+
+  - Use #underscore, not #downcase for help text scope (#140, @atipugin)
+  - Radio button and checkbox labels will now include the disabled class as needed. (#156, @ScottSwezey)
+  - Fixed issue with setting offset in form_group without label in horizontal layout
+    when form uses non-default label_col
+  - Fixed wrapper options (#153, @veilleperso)
+  - Fix errors on non-ActiveRecord setups (#200, @sgnn7)
+
+Features:
+
+  - Allow users to display validation errors in labels (#144, @timcheadle)
+  - Use humanized attribute name in label errors (#146, @atipugin)
+  - Allow to skip label rendering (#145, @atipugin)
+  - Added a `required` CSS class for labels with required attributes (#150, @krsyoung)
+  - Added option to customize labels' class.
+  - Allow callable value_method and text_method for collection_check_boxes and collection_radio_buttons (#199, @shadwell)
+
+## 2.2.0 (2014-09-16)
+
+Bugfixes:
+
+  - Fixed an exception raised when form_group block returns nil (#111)
+  - Fixed an exception on human_attribute_name when using bootstrap_form_tag (#115)
+  - Set offset in form_group without label in horizontal layout (#94, @datWav)
+  - Fixes an offset bug in form_group without a given label in horizontal layout (#130, @datWav)
+  - Fixed bug where collection_check_boxes doesn't work if all are unchecked (#116, @burnt43)
+
+Features:
+
+  - Added the ability to append/prepend buttons (@retoo)
+  - Added support for time_zone_select
+  - Accept multiple values, and objects as well, on `collection_check_boxes`
+    checked option (#114)
+  - Added support for hidding attribute name in errors_on helper (@datWav)
+  - Added support for additional class to the wrapper form_group by a field (@datWav)
+  - Support showing error summaries when inline_errors is enabled (@rosswilson)
+  - Name is now optional when creating static controls
+  - Keep original form helper methods with _without_bootstrap suffix (#123, @a2ikm)
+  - Added glyphicon support
+  - Added i18n support for help messages (#122, @huynhquancam)
+  - Added the ability to pass any attributes to wrapper (#136, @atipugin)
+  - Split monolithic test file into several smaller files (#141, @spacewander)
+  - Added role="form" attribute to forms (#142, @spacewander)
+
+## 2.1.1 (2014-04-20)
+
+Bugfixes:
+
+  - Do not reset additional classes on the form-group (@rzane)
+  - Fixed an exception when specifying a label while using bootstrap_form_tag
+
+Features:
+
+  - [nested_form](https://github.com/ryanb/nested_form) integration via
+    `bootstrap_nested_form_for` (#44 and #66)
+  - `form_group` no longer requires a name (#83)
+
+## 2.1.0 (2014-04-01)
+
+Moved GitHub repository from https://github.com/potenza/bootstrap_form
+to https://github.com/bootstrap-ruby/bootstrap_form
+
+Bugfixes:
+
+  - i18n fix for checkbox labels (@i10a)
+  - Wrapped date & time helpers inside control-specific css classes to prevent stacking
+  - control-label class was not being added unless the form was horizontal (@slave2zeros)
+  - selects & collection selects were dropping label options
+  - allow html content in check_box tag label (@desheikh)
+  - allow check_box label to be defined with a block
+  - omit form-control class from file_field (@mbrictson)
+  - Collection inputs honour `checked` attribute (@desheikh)
+  - Fixing label/input pairing for checkbox collections (@byped)
+  - Removing for attribute on radio button labels (@sigmike)
+
+Features:
+
+  - The control_class can be overridden per field by passing in the
+    :control_class option. Default value is "form-control".
+  - Make name optional in FormBuilder#submit (@adrpac)
+  - Added the FormBuilder#primary helper back in
+  - Added a FormBuilder#static_control helper
+  - Added support for radio_buttons_collection and check_boxes_collection
+  - Added a FormBuilder#error_summary helper method
+  - inline_errors can be turned off: bootstrap_form_for(obj, inline_errors: false)
+    When inline errors are off, FormBuilder#alert_message contains the error summary.
+    This can also be turned off with the option 'error_summary: false'
+  - Added support for: color_field, date_field, datetime_field, datetime_local_field,
+    month_field, range_field, search_field (#42), time_field, week_field
+  - Added ability to override the left/right classes for a particular control
+    when using horizontal forms. (@baldwindavid)
+  - Added support for grouped_collection_select (@rzane)
+  - Added support of Rails 4 syntax for collection inputs (@desheikh)
+  - Renamed options :left to :label_col and :right to :control_col
+  - Renamed option :style to :layout (@baldwindavid)
+  - Added errors_on helper (@baldwindavid)
+  - Added per field layout option (@baldwindavid)
+  - Added support for bootstrap_form_tag (@baldwindavid)
+
+
+[Pending Release]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v2.7.0...HEAD
+[2.7.0]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v2.6.0...v2.7.0
+[2.6.0]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v2.5.3...v2.6.0
+[2.5.3]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v2.5.2...v2.5.3
+[2.5.2]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v2.5.1...v2.5.2
+[2.5.1]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v2.5.0...v2.5.1
+[2.5.0]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v2.4.0...v2.5.0
+[2.4.0]: https://github.com/bootstrap-ruby/bootstrap_form/compare/v2.3.0...v2.4.0

data/CONTRIBUTING.md

@@ -0,0 +1,57 @@
+# Contributing
+
+The release of Bootstrap 4 and Rails 5.1 have implications for the future
+direction of `bootstrap_form`. Don't worry. We plan to move this gem forward to
+Bootstrap 4 and to support Rails 5.1 and beyond. If you're thinking of
+contributing to `bootstrap_form`, please read
+[issue #361](https://github.com/bootstrap-ruby/bootstrap_form/issues/361).
+
+Your comments are welcome.
+
+Thanks so much for considering a contribution to bootstrap_form. We love pull requests!
+
+Here's a quick guide for contributing:
+
+### 1. Check if issue or feature is available to work on
+
+Make sure no one else is working on the same issue or feature. Search the issues
+and pull requests for anything that looks like the issue or feature you want to
+address. If no one else is working on your issue or feature, carry on with the
+following steps.
+
+### 2. Fork the repo
+
+For the project. Optionally, create a branch you want to work on
+
+### 3. Get it running locally
+
+- Install the required dependencies with `bundle install`
+- Run tests via: `bundle exec rake`
+
+### 4. Hack away
+
+- Try to keep your changes small. Consider making several smaller pull requests.
+- Don't forget to add necessary tests.
+- Update the README if necessary.
+- Add a line to the CHANGELOG for your bug fix or feature.
+
+You may find using demo application useful for development and debugging.
+
+- `cd demo`
+- `rake db:schema:load`
+- `rails s`
+- Navigate to http://localhost:3000
+
+### 5. Make a Pull Request
+
+- If you never done it before read this: https://help.github.com/articles/about-pull-requests/
+- When PR is submitted check if TravisCI ran all tests successfully didn't raise any issues
+
+### 6. Done!
+
+Somebody will shortly review your pull request and if everything is good will be
+merged into master brach. Eventually gem will be published with your changes.
+
+---
+
+Thanks to all the great contributors over the years: https://github.com/bootstrap-ruby/bootstrap_form/graphs/contributors

data/Dangerfile

@@ -0,0 +1,54 @@
+# Adapted from https://github.com/ruby-grape/danger/blob/master/Dangerfile
+# Q: What is a Dangerfile, anyway? A: See http://danger.systems/
+
+# ------------------------------------------------------------------------------
+# Additional pull request data
+# ------------------------------------------------------------------------------
+project_name = github.pr_json["base"]["repo"]["name"]
+pr_number = github.pr_json["number"]
+pr_url = github.pr_json["_links"]["html"]["href"]
+
+# ------------------------------------------------------------------------------
+# What changed?
+# ------------------------------------------------------------------------------
+has_lib_changes = !git.modified_files.grep(/^lib/).empty?
+has_test_changes = !git.modified_files.grep(/^test/).empty?
+has_changelog_changes = git.modified_files.include?("CHANGELOG.md")
+
+# ------------------------------------------------------------------------------
+# You've made changes to lib, but didn't write any tests?
+# ------------------------------------------------------------------------------
+if has_lib_changes && !has_test_changes
+  warn("There are code changes, but no corresponding tests. "\
+       "Please include tests if this PR introduces any modifications in "\
+       "#{project_name}'s behavior.",
+       :sticky => false)
+end
+
+# ------------------------------------------------------------------------------
+# Have you updated CHANGELOG.md?
+# ------------------------------------------------------------------------------
+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):
+
+```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), "\
+       "you can disregard this.", :sticky => false)
+end
+
+# ------------------------------------------------------------------------------
+# Did you remove the CHANGELOG's "Your contribution here!" line?
+# ------------------------------------------------------------------------------
+if has_changelog_changes
+  if IO.read("CHANGELOG.md").scan(/^\s*[-\*] Your contribution here/i).count < 3
+    fail(
+      "Please put the `- Your contribution here!` line back into CHANGELOG.md.",
+      :sticky => false
+    )
+  end
+end

data/Gemfile

@@ -0,0 +1,21 @@
+source "http://rubygems.org"
+
+gemspec
+
+# Uncomment and change rails version for testing purposes
+# gem "rails", "~> 5.2.0.beta2"
+
+group :development do
+  gem "htmlbeautifier"
+end
+
+group :test do
+  # can relax version requirement for Rails 5.2.beta3+
+  gem "minitest"
+
+  gem "diffy"
+  gem "equivalent-xml"
+  gem "mocha"
+  gem "sqlite3"
+  gem "timecop"
+end

data/LICENSE.txt

@@ -0,0 +1,20 @@
+Copyright 2012-2018 Stephen Potenza <potenza@gmail.com>
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,647 @@
+⚠️ **This documentation is for the master branch, which is not yet stable and 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.
+
+---
+
+# 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.0+
+* Rails 4.0+ (Rails 5.1+ for `bootstrap_form_with`)
+* Bootstrap 4.0.0+
+
+## Installation
+
+Add it to your Gemfile:
+
+```ruby
+gem "bootstrap_form",
+    git: "https://github.com/xire28/bootstrap_form.git",
+    branch: "master"
+```
+
+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
+* search_field
+* select
+* telephone_field
+* text_area
+* text_field
+* time_field
+* time_select
+* time_zone_select
+* url_field
+* week_field
+
+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" %>
+```
+
+#### 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 `skip_required` option:
+
+```erb
+<%= f.password_field :password, label: "New Password", skip_required: true %>
+```
+
+### 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' }`.
+
+### 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:" }, { class: "selectpicker",  wrapper: { class: 'has-warning', data: { foo: 'bar' } } } %>
+```
+
+### 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 %>
+```
+
+#### Collections
+
+`bootstrap_form` also provides helpers that automatically creates 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" do %>
+  Content Here
+<% end %>
+```
+
+### 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" %>
+```
+
+### 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 %>
+```
+
+### 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
+
+## 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)