Rails 1.2RC1: To Jump or Not To Jump?
Author: ceefour | Filed under: Opinions, Rails, Ruby, Tips, Web 2.0Okay, so Rails 1.2RC1 is out. After some early experimentation, I found it to be quite “unusable” in its current state. It’s good, but the level of support other software provide for this version of Rails is quite minimal. Read on for explanation.
The one feature in Rails 1.2 that I like best is resource-based controllers that implements REST APIs. You can use:
map.resources :items
So that your ItemsController handles REST APIs, and they’re automatically mapped to actions like new, create, edit, update, delete, show, etc. And Rails also provide named routes too, so item_url(53) will give you something like /items/53 that goes to your items/show action. Funky!
Therefore it’s a no problemo. The only problem(s) are actually other software, like plugins, and RadRails. RadRails doesn’t start the Webrick server correctly on Rails 1.2RC1. Rails Engines plugin doesn’t work, at least for the routes. This happens to the ActiveRbac engine, which I [always] use. Same problem for theme_support plugin.
That is, if only for the REST support, I’ll upgrade to Rails 1.2 later when support is more solid. Sticking with 1.1.6 for now, even for toy projects. If you want to ease migration to Rails 1.2 with resource controllers, make sure to name your actions accordingly: create, new, edit, show, update, delete, (any more?). And use named routes. So when you finally upgrade to Rails 1.2 you don’t have to change too many things to use its capabilities.
Technorati : migration, radrails, rails, review, reviews, ruby, rubyonrails, test, tests, theme support, upgrade, webrick
Del.icio.us : migration, radrails, rails, review, reviews, ruby, rubyonrails, test, tests, theme support, upgrade, webrick
Ice Rocket : migration, radrails, rails, review, reviews, ruby, rubyonrails, test, tests, theme support, upgrade, webrick
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.