Feature #59
Re-implement url_for via this_blog.base_url
| Status : | Closed | Start : | ||
| Priority : | Urgent | Due date : | ||
| Assigned to : | scott - | % Done : | 0% |
|
| Category : | frontend | |||
| Target version : | Maybe Someday | |||
| Resolution : | fixed |
Description
You know, the only reason we have to carry the controller around all of the place is to get at the base URL for url_for (and variants thereof). The blog object contains the "official" base URL. Therefore, we should build our own blog.url_for. That'll get rid of a hundred lines of cruft, about 20 layering violations, and probably be faster, too.
Associated revisions
Revision 9f6b58a1ccf1a38892871b1cb42b8283a2b53b36
added 43things aggregation thanks to Anoop Ranganath (fixes #59)
git-svn-id: http://svn.typosphere.org/typo/trunk@209 820eb932-12ee-0310-9ca8-eeb645f39767
History
08/20/2006 10:15 AM - anonymous -
I'm a bit concerned that the new blog.url_for brings controllers directly into models in what seems like a violation of MVC.
Is this the optimal solution? It looks like a prime candidate for RESTful urls using controllers and routes.rb.