The thing about the semicolon is how nicely it played with to_param'd
resource identifiers.
Take this:
map.resources :users
And a to_param on User:
class User < ActiveRecord::Base
alias_attribute :to_param, :name
end
And a find_by_name in our UsersController.
Now we get /users/chris and /users/chris/edit as expected. Works
great. But what about our 'Popular Members' page? /users/popular?
Major namespace clash, now and in the future (when we add new
features).
This is a shame because Rails makes it so easy to use a name (or
title) as the resource identifier.
Has anyone run into this issue and is there a sanctioned way to handle
it? I'd ask for the semicolon back, but I doubt that'll happen.
- Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---
