News for hackers. Stuff that matters.

A comment on Rethinking Rails 3 Controllers and Routes - PeepCode Blog. Parent comment

Re:Rethinking Rails 3 Controllers and Routes - PeepCode Blog by dkubb on Thursday June 03, 2010 @03:38AM (#1400744)
Whenever I've tried to reuse the same controller for two URLs, I usually end up with some conditional logic within the controller to handle difference in parameters available from the URL.

I think a better approach would've been for me to subclass one from the other, or have a common parent class, and then handle the parameter differences within each subclass. At that point you'd end up with a 1:1 mapping between controller class and URL anyway.

[ Parent | on HN ]
Re:Rethinking Rails 3 Controllers and Routes - PeepCode Blog by mikek85 on Monday June 07, 2010 @02:00PM (#1411210)
That 1:1 mapping is a good thing, but I don't think that's a reason to completely do-away with routing altogether. Sticking the route in the controller just makes the code harder to follow.
[ Parent | on HN ]