Fortitude v0.9.6 Release NotesRelease Date: 2016-10-21 // almost 5 years ago
- 👍 Generator support: generation of controllers, mailers, and scaffolding will now produce nice Fortitude views
instead of ERb views. (You can add
-e erbto your
rails generatecommand line to switch back to ERb if desired.) Thanks to Gaelan for the suggestion!
- 🛠 Fixed an issue where if you tried to invoke methods on the object yielded to a
form_forcall or similar by using
sendinstead of calling it directly (e.g.,
form_for(...) do |f|, then
f.send(:text_field, ...)instead of
f.text_field ...), the method invocation would appear to be ignored.
- Fixed an issue where Rails
_pathhelpers didn't correctly pick up parameters set from the incoming request. (Thanks to Adam Becker for the bug report!)
- 👍 Generator support: generation of controllers, mailers, and scaffolding will now produce nice Fortitude views instead of ERb views. (You can add
Previous changes from v0.9.5
- 🚅 Rails 5 compatibility: Fortitude now is fully compatible with Rails 22.214.171.124.
- 🐎 Significant improvements in performance to our dispatching to #t, the Rails method to produce translations of localized strings. Localized Rails applications tend to use this method a lot, so its performance can have a big impact on overall application performance.
- 👍 A much better error message if you try to declare a method
staticwhen it hasn't been defined yet — this can often be the result of putting the
staticdeclaration above the method definition in the source file, rather than below it. (Thanks to
tobymaofor the bug report!)
- ⚡️ Updated versions of Ruby and Rails that Travis CI tests against to the very latest.
- 🛠 Fixed an issue where Fortitude wasn't properly respecting Rails' view paths. Fortitude templates could be found at
alternate view paths, but our trick of namespacing views under
Views::wouldn't apply. Now, it all works perfectly. (Thanks to Karl He for the bug report and example patch!)
- 🛠 Fixed an issue where
trueinside a Fortitude widget's
#contentmethod, whether a block was supplied to it or not. (Thanks to Jeff Dickey for the bug report!)
- 🛠 Fixed an incompatibility between Fortitude and Rails 126.96.36.199, since Rails 188.8.131.52 added a fifth parameter to
ActionView::PathResolver#find_templates. (Thanks to Luke Francl for the bug report!)
- 🛠 Fixed incompatibilities with more-recently released versions of gems (
activesupport) that otherwise broke compatibility with previous Ruby versions.
- 🛠 Fixed an issue where Fortitude’s system for figuring out what the name of a Fortitude widget would be, based on its
filename, could be confused by filenames ending in other extensions before
- 🗄 Eliminated a deprecation warning from Rails 5 caused by Fortitude's use of
- Removed usage of
alias_method_chainon Ruby 2.0 and later, in favor of
Module#prepend. This removes deprecation warnings otherwise triggered by Rails 5. (Using
Module#prependcauses problems in JRuby, so
alias_method_chainis still used on JRuby instead.)
- Changed the behavior of
automatic_helper_access falseso that, in a Rails application, it still makes all the built-in Rails helpers properly accessible, but does not make user-defined helpers accessible. (If there are even certain built-in Rails helpers you don’t want people using, you can easily override them in your widget class to raise an exception.) Without this,
automatic_helper_access falsebecame so cumbersome to use that it was nearly pointless. (Thanks to Matt Walters for the pull request!)
- Fixed an issue where explicitly declaring an assignment method as a helper (e.g.,
helper :foo=) did not work properly.
- Fixed an issue where passing a block to (e.g.)
fis the object yielded to a
form_forhelper, did not work properly. (Thanks to Adam Becker for the bug report and test case!)
- ⬇️ Reduced escaping in attribute values: only
&need to be escaped, not
'. (Thanks to Adam Becker for the bug report!)
- 🛠 Fixed an issue where, under certain extremely rare circumstances, adding a view path in the controller (using
ActionView::ViewPaths.append_view_pathand related methods) would not be able to figure out the proper class name of the widget, and would fail. (Thanks to Leaf for the bug report!)
- ➕ Added the ability for the
inline_htmlmethod on a widget class to accept a
Fortitude::RenderingContext, thus allowing you to use it with code requiring access to helpers. (Thanks to Adam Becker for the bug report!)