So I’m learning the latest Rails release by converting an existing app to it. This app used namespaced controllers for its admin section.
New routes features have really cleaned this up.
map.resources :users, :controller => 'admin/users', :name_prefix => 'admin_', :path_prefix => 'admin'
map.namespace(:admin) do |admin| admin.resources :users end
Then I began to take advantage of Rails 2.0’s smarter #formfor courtesy of simplehelpful in the non-admin portion of the app.
<% form_for @user do |form| %> <% end %>
user object is a #newrecord? that #formfor is going to generate the following html:
user object is not a #newrecord? that #formfor is going to generate the following html (assuming its id is 1):
Now let’s look at the #new and #edit forms for the admin section of the site.
<% form_for [:admin, @user] do |form| %> <% end %>
This will generate the same html as above except with ‘/admin’ being prefixed onto each
action attribute value.
Ooo that is ugly.
Some more examples.
redirect_to [:admin, @user] # redirect_to admin_user_url link_to 'show', [:admin, @user] # link_to 'show', admin_user_url
Array syntax seems like such a quick hack, like they forgot about namespaced controllers. With all the nice interfaces in Rails, this one really sticks out. I’m willing to bet this becomes deprecated in the near future.
In the meantime I’m going to stick with the much better looking old style.
<% form_for @user, :url => admin_user_url do |form| %> <% end %>
However, this sucks because I’d really like to take advantage of these smarter #formfor, #redirectto and #link_to versions but I consider consistency in my code more important. I’d rather see 1 consistent way of using named routes instead of using them solely in the namespaced controller sections of an app in order to avoid this new ugly syntax.
This would probably be a lot cleaner in php.