Rails, as you probably know, is under active development. So, for those of you who don’t have time to read every commit to the source, we’ve decided to revive this section of the weblog. This time around, I’m covering 3 weeks of commits: the time since Rails 2.2 RC1 (otherwise known as Rails 2.2.0) was released. Though there aren’t any major new features being added as Rails drives towards the 2.2 release, that doesn’t mean the source has been completely quiet: there have been about 75 commits in that three-week period. Here’s a look at some of those changes.
In the run-up to 2.2, we’re seeing a batch of little bug fixes, as people try to ensure quality in the release. These include:
- Squashing a binary data corruption bug that surfaced in the PostgreSQL adapter. commit
- The regex behind redirect_to can now accept a wider variety of URL schemes, making it possible to redirect to some destinations that were previously inaccessible. commit
- A regression in date_select and datetime_select that could raise a Null Pointer Exception under some circumstances has been fixed. commit
- The sanitize helper has been fixed to avoid double escaping already properly escaped entities. commit
- FormTagHelper has been stopped from generating illegal HTML if the name contains square brackets. commit
- A memory leak was squashed in Active Record scoped methods. commit
Some of the major features for 2.2 have been getting fine-tuned as well. There’s been work to clean up some loose ends in the thread safety department, and changes to make the I18n backend reload its translations in development mode. The included Prototype bits were bumped to the latest 126.96.36.199 release. The code for configuring, loading, and vendoring gems has had some attention, and the code for maintaining database connection pools has come in for some fine-tuning as well.
Just because we’re in feature freeze doesn’t mean that a few new features can’t sneak in:
- The current_page method is a bit more reliable now in that it ignores options you don’t explicitly supply (making it more friendly to URLs that use the query string for pagination and the like). commit
- The default logging has been cleaned up to be less chatty: you’ll see fewer duplicate log messages as Rails goes about its business. commit
- The render method now takes a
- If you’ve got a current (Ruby 1.8.7 or greater) version of Ruby, Action Mailer turns on
STARTTLS if the server supports it; this makes Action Mailer compatible with GMail without the need for plugins. commit
One final note: I’m deliberately not trying to cover every single commit here; just those ones that struck me as most interesting. But if I left out something that you think is highly significant, feel free to add a pointer in the comments!