Formtastic 1.0 Release

Published 12 August 10 by Justin French

After promising we’re “deliciously close to a 1.0” for about a year, this has been a long time coming.

Formtastic 1.0 is compatible with Rails 2.x. For those of you working with Rails 3, there’s a rails3 branch (aiming to be compatible with both Rails 2.x and 3.x) on Github, and we hope to ship a 1.1.0.beta gem in the next week or so from this branch.

From here on, I’d like to adhere Semantic Versioning.

If you haven’t been playing with the betas and release candidates (shame on you!), here’s a quick re-cap of what’s changed since 0.9.10:

• Fixed that :label=>false didn’t disable the label on checkboxes & radio buttons
• Added full support of :input_html options for hidden fields
• Fixed that :checked_value and :unchecked_value options were being passed down into the HTML tags as attributes
• ensure i18n < 0.4 is listed as a dependency in the gemspec
• Added :ignore_date option to time inputs
• Fixed some issues with the default error proc
• Added default escaping of html entities in labels and hints
• Added/fixed that :value_method and :label_method were being ignored for simple collections (like an Array)
• Added some more compatibility for Mongoid and other ORMs by checking for reflection information before calling it
• Fixed deprecation warnings in Rails 2.3.6 and newer
• Fixed a bug where :check_boxes and :radio inputs were using the attribute name instead of the :label option
• Fixed a conflict where i18n lookups were failing when an attribute and model have the same name
• Fixed :radio and :check_boxes inputs so that the legend no longer includes a <label> with a for attribute pointing to an input that doesn’t exist
• Fixed that some inputs had invalid find_options HTML attribute
• Fixed that we were calling html_safe! when it was not always available
• Added the ability for :input_html to now accept an option of :size => nil, to exclude the :size attribute altogether

The really exciting thing for me is that there’s been over 60 contributors to the project. Tools like Github make this easier, but real people donating their time actually makes it work.

The community is almost entirely responsible for the rails3 branch too — I started using it for the first time on a new project last month and it was so great to see how far along we are, and most importantly, how little I had to do myself to make it happen.

So, thank you all for the support, the bug reports, the patches, the testing, the polishing, the feature requests, the rants, the complaining, the praise, the promotion, the donations and the awesomeness.