Singular resource controller naming convention changed?


#1

Hi,

singular resources used to assume singular controller naming, as in:

map.resources :session
GET /session/ {:action=>“show”, :controller=>“session”}

did this change in edge? My routes broke after updating, and now I get:

GET /session/ {:action=>“show”, :controller=>“sessions”}

(‘sessions’ instead of ‘session’)

Was that a decision made, or might this be a bug?

Ingo


#2

I think is a wanted change.

http://groups.google.com/group/rubyonrails-core/browse_thread/thread/b55030e18e52bc98

Paolo


#3

Thanks, Paolo! This thread explains it!

Ingo