Drag your legacy Rails apps into the future a little more easily.
Upgrading a legacy Rails app can be a frustrating process. Ideally, you'd like to break the upgrade up into as many discrete steps as possible: upgrade the Ruby version here, a couple gems there, and continually commit to master with all tests passing at each step.
But these intermediate steps often involve version combinations that are not well supported or tested (e.g. Ruby 2 + Rails 2), and a lot of time is typically spent tracking down unexpected test failures and cryptic error messages that result from these dangerous version combinations.
Rails-futurizer makes the upgrade process quicker and easier by automatically patching some of these bugs and giving clear warnings about the cause of others. See below for a list of all patches and warnings available.
It doesn't backport any features or syntax from newer Ruby/Rails versions to older versions. Upgrade your apps; don't keep developing them against old versions.
-
Ruby 1.8.7 or greater
-
RubyGems 1.1.0 or greater
-
Nothing else. But rails-futurizer won't do anything unless it's installed alongside a version of Rails for which some applicable fixes are available.
If your app is using Bundler, add the rails-futurizer gem to the Gemfile.
gem "rails-futurizer"
Then update your bundle.
$ bundle
That's it! Rails-futurizer will automatically activate any fixes and warnings that are applicable to the currently installed versions of Ruby and Rails, and ignore those that are not applicable.
(If your app is too old to be using Bundler, consider adding Bundler as the first step toward upgrading.)
The following bugs will be automatically patched when rails-futurizer is loaded.
-
When Rails 2.3 or older is used with Ruby 2.0 or newer, parameter log filtering in ActionController silently fails, causing all parameters to be logged regardless of filter settings. Patched for Rails 2.2.1 or newer.
-
When Rails 2.2 - 3.0 is used with Ruby 2.0 or newer, saving an ActiveRecord model that has an array assigned to one of its has_many associations will raise the exception "undefined method 'insert_record' for Array". Patched for all affected versions.