Hobo's automatic routing needs to be more customisable
Reported by Tom | April 2nd, 2008 @ 09:57 AM | in Beyond Hobo 1.0
Comments and changes to this ticket
-
Tom Locke July 29th, 2008 @ 10:52 AM
- State changed from new to open
- Tag set to routing
- Milestone set to Hobo 1.0 - Final
-
Tom Locke January 7th, 2009 @ 11:42 AM
- Tag changed from routing to enhancement, misc, routing
- Milestone changed from Hobo 1.0 - Final to Beyond Hobo 1.0
-
averell23 April 19th, 2010 @ 04:21 PM
Since there was no followup on this on the mailing list, I'll file it on the ticket. I'm not 100% certain if it is the same problem, but it's certainly related.
The point is that the automatic routing, surprisingly, does use the Model class names and namespaces to create the routes. However, since routes go to controllers, this makes it essentially impossible to use a hobo controller with a model class of a different name.
I ran into that while trying to build an admin interface for an existing set of model classes, which, for this reason, doesn't really work.
As it is, I'd say the feature is broken for all but the default case (ControllerName == ModelName).
I also haven't seen any reason why the routing is tied to the models instead of the controllers. First, it creates additional dependencies between the model and the presentation. Then all routing in Rails is always to the controller classes and rewiring it appears to cause pain.
-
Tom Locke April 19th, 2010 @ 04:31 PM
Agreed this was definitely a mistake, and needs fixing. I created a separate ticket #705, for this issue
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
People watching this ticket
Tags
Referenced by
- 705 Controllers, not models, should be used to generate routes See the comment in #7 that led to this ticket