Skip to content

Releases: bootstrap-ruby/bootstrap_form

4.5.0

30 Apr 01:33
Compare
Choose a tag to compare

New features

4.4.0

08 Mar 21:53
Compare
Choose a tag to compare

New features

  • #557: Allow prepending and appending multiple items to an input by passing an array to prepend and append options - @donv.
  • #550: Add default_layout so we can use it for all forms - @duleorlovic.

Bugfixes

  • Your contribution here!

4.3.0

22 Sep 00:01
Compare
Choose a tag to compare

New features

  • [#503] Support Rails 6.0.0.
  • Small documentation changes.

4.2.0

08 Mar 15:50
Compare
Choose a tag to compare

New features

  • [#508] Support rich_text_area AKA the Trix editor on Rails 6+.
  • [#518] Move all inputs to separate, more maintainable files.
  • #514: Add support for BS 4.2 switches - @simmerz

Bugfixes

4.1.0

19 Jan 17:35
Compare
Choose a tag to compare

New features

Bugfixes

  • [#496] Ensure required attribute is passed through to input tag.

4.0.0

27 Oct 15:04
ff7ad3a
Compare
Choose a tag to compare

🚨 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 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

New features

  • [#476] Give a way to pass classes to the div.form-check wrapper for check boxes and radio buttons - @lcreid.
  • 461: default form-inline class applied to parent content div on date select helpers. Can override with a :skip_inline option on the field helper - @lancecarlson.
  • The button, submit, and primary helpers can now receive an additional option, extra_class. This option allows us to specify additional CSS classes to be added to the corresponding button/input, while maintaining the original default ones. E.g., a primary button with an extra_class 'test-button' will have its final CSS classes declaration as 'btn btn-primary test-button'.

Bugfixes

  • #347 Fix wrapper_class and wrapper options for helpers that have html_options.
  • #472 Use id option value as for attribute of label for custom checkboxes and radio buttons.
  • #478 Fix offset for form group without label when multiple label widths are specified.

4.0.0.alpha1

16 Jun 17:43
Compare
Choose a tag to compare

🚨 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 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.
  • form_group with a block that produces arbitrary text needs to be modified to produce validation error messages (see the UPGRADE-4.0 document). @lcreid.
  • form_group with a block that contains more than one check_box or radio_button needs to be modified to produce validation error messages (see the UPGRADE-4.0 document). @lcreid.
  • #456: Fix label for attribute when passing non-english characters using collection_check_boxes - @ug0.
  • #449: Bootstrap 4 no longer mixes in .row in .form-group. bootstrap_form adds .row to div.form-group when layout is horizontal.

New features

  • Support for Rails 5.1 form_with - @lcreid.
  • Support Bootstrap v4's Custom Checkboxes and Radios with a new custom: true option
  • Allow HTML in help translations by using the _html suffix on the key - @unikitty37
  • #408: Add option[:id] on static control #245 - @duleorlovic.
  • #455: Support for i18n :html subkeys in help text - @jsaraiva.
  • Adds support for label_as_placeholder option, which will set the label text as an input fields placeholder (and hiding the label for sr_only).
  • #449: Passing .form-row overrides default .form-group.row in horizontal layouts.
  • Added an option to the submit (and primary, by transitivity) form tag helper, render_as_button, which when truthy makes the submit button render as a button instead of an input. This allows you to easily provide further styling to your form submission buttons, without requiring you to reinvent the wheel and use the button helper (and having to manually insert the typical Bootstrap classes). - @jsaraiva.
  • Add :error_message option to check_box and radio_button, so they can output validation error messages if needed. @lcreid.

Bugfixes

  • #357 if provided,
    use html option id to specify for attribute on label
    @duleorlovic

2.7.0

21 Apr 15:12
Compare
Choose a tag to compare

Features:

  • #325: Support :prepend and :append for the select helper - @donv.

2.6.0

03 Feb 15:25
Compare
Choose a tag to compare

Bugfixes:

  • None

Features:

  • Add a FormBuilder#custom_control helper #289

2.5.3

23 Dec 18:37
Compare
Choose a tag to compare

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).