What's New in Edge Rails: Rails 2.2 Released - Summary of Features

Posted by ryan
at 8:13 PM on Friday, October 24, 2008
I’ve updated this post to reflect the features added after RC1, so consider this to be a full list of major 2.2 features

Rails 2.2 (RC1) was just released, let’s take a peek at some of the major new features (as determined by yours truly – feel free to pipe up with features that I’ve missed).

Rails 2.2.2 requires rubygems v 1.3.1, so before you upgrade make sure to do a sudo gem update --system.

Rails 2.2 Features

Note: The nested model mass assignment feature previously discussed has been delayed until after this 2.2 release. Just needs a little more time in the oven, apparently.

Enjoy, folks.

tags: ruby, rubyonrails

Comments

Leave a response

  1. Tom – October 25, 2008 @ 03:45 AM

    Great stuff, but your post about the :shallow option is still wrong, and it’s going to cause some real confusion among Rails newbies (your target audience).

    “This configuration keeps all the normal nested routes” is NOT TRUE. :shallow does NOT generate the nested routes for show, edit, update and destroy—it MOVES them to the non-nested position.

    You’re telling people that :shallow generates extra routes, but actually it generates exactly the same number of routes, just in a non-nested position when the resource ID is specified.

  2. Mark – October 25, 2008 @ 11:08 AM

    Thank you Ryan!

  3. Ryan Daigle – October 25, 2008 @ 11:59 AM

    Tom – you’re absolutely right. I’ve updated the original post to be more clear about what routes are generated. Thanks for the catch.

    -Ryan

  4. Peter Wagenet – October 25, 2008 @ 09:04 PM

    In your post on “Custom Length Validation Tokenizer” you say “the default behavior is to just count the number of characters in the attribute value”. While it does indeed do this, if it is unable to count the number of characters (say the passed value is not a string), it will fall back to calling #size on the passed object. But it’s great to see that we have even more flexibility now.

  5. Michael – November 22, 2008 @ 09:29 PM

    Thanks Ryan! I appreciate all the work you put into your blog.

  6. Piyush – December 19, 2008 @ 03:00 AM

    Efforts appreciated , like the new version 2.2 and the links here are a good reason why.Thanx

  7. Slep – January 09, 2009 @ 11:36 AM

    I think you can also mention new migrations naming convention. Now it has timestamp instead of sequence number. This allows easy branch merging.