7211 0 true 2008-09-04T14:43:31+01:00 1366 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 19700 16213 published 2010-01-24T16:58:18+00:00 83786 psi Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 Routing from the outside in. Cover the user-facing features of routing. Routing from the outside in. Cover the user-facing features of routing. <div><p>Routing from the outside in. Cover the user-facing features of routing.</p></div> 1366 0 Routing from the outside in. Cover the user-facing features of routing. <div><p>Routing from the outside in. Cover the user-facing features of routing.</p></div> false 2008-09-04T14:43:32+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 new routing 2008-09-04T14:43:32+01:00 1366 Pratik Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 I've committed a version of this to docrails, ready for review. I know of a couple of typos that need to be fixed (drat, proofing twice wasn't enough) but I'd be happy for any more substantive feedback. guides/routing/routing_outside_in.txt <div><p>I've committed a version of this to docrails, ready for review. I know of a couple of typos that need to be fixed (drat, proofing twice wasn't enough) but I'd be happy for any more substantive feedback.</p> <p>guides/routing/routing_outside_in.txt</p></div> false 2008-09-04T16:39:10+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing-2 0 16213 new routing 2008-09-04T16:39:10+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Mike, I'd remove the analogy here (or change it to something else): @@@ Rails routing is a two-way piece of machinery - rather as if you could turn pigs into sausage, and then turn sausage back into pigs. @@@ It could be inappropriate for some audiences. Also in this chapter: @@@ link_to "Patient Record", patient_path(@patient) @@@ It should be noted that patient has to be declared a resource for the named route to be available. In Chapters 2 and 4, you are labeling regular routes as being "old-style". This will discourage people from using them, thinking they are deprecated or obsolete in some way. Regular routes still (and always will) have their usages; it's just that RESTful routes should be preferred *when possible*. In Chapter 3, you're saying that RESTful routes are "the new standard" in Rails. Because the target audience for these guides are newcomers that will get started with Rails 2.1 anyway, I don't think it matters to them that this is something "new". I think you should just point out that they are encouraged and preferred. I'd also rename "Dumping Routes with rake" to something like "How to inspecting existing routes" <div><p>Mike,</p> <p>I'd remove the analogy here (or change it to something else):</p> <pre><code> Rails routing is a two-way piece of machinery - rather as if you could turn pigs into sausage, and then turn sausage back into pigs. </code></pre> <p>It could be inappropriate for some audiences.</p> <p>Also in this chapter:</p> <pre><code> link_to &quot;Patient Record&quot;, patient_path(@patient) </code></pre> <p>It should be noted that patient has to be declared a resource for the named route to be available.</p> <p>In Chapters 2 and 4, you are labeling regular routes as being "old-style". This will discourage people from using them, thinking they are deprecated or obsolete in some way. Regular routes still (and always will) have their usages; it's just that RESTful routes should be preferred <em>when possible</em>.</p> <p>In Chapter 3, you're saying that RESTful routes are "the new standard" in Rails. Because the target audience for these guides are newcomers that will get started with Rails 2.1 anyway, I don't think it matters to them that this is something "new". I think you should just point out that they are encouraged and preferred.</p> <p>I'd also rename "Dumping Routes with rake" to something like "How to inspecting existing routes"</p></div> false 2008-09-04T17:17:04+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing-3 0 16213 new routing 2008-09-04T17:17:04+01:00 192 Mislav Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Hey Mike, It's pretty awesome. Mislav has valid points too. Also, the guide should mention 2-3 lines about testing routes and link http://api.rubyonrails.com/classes/ActionController/Assertions/RoutingAssertions.html Thanks! <div><p>Hey Mike,</p> <p>It's pretty awesome. Mislav has valid points too.</p> <p>Also, the guide should mention 2-3 lines about testing routes and link <a href="http://api.rubyonrails.com/classes/ActionController/Assertions/RoutingAssertions.html"> http://api.rubyonrails.com/class...</a></p> <p>Thanks!</p></div> false 2008-09-05T03:55:27+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing-4 0 16213 new routing 2008-09-05T03:55:27+01:00 1366 Pratik Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Also, we should advice users not to nest more than 1 level as a rule of thumb. http://weblog.jamisbuck.org/2007/2/5/nesting-resources <div><p>Also, we should advice users not to nest more than 1 level as a rule of thumb. <a href="http://weblog.jamisbuck.org/2007/2/5/nesting-resources">http://weblog.jamisbuck.org/2007...</a></p></div> false 2008-09-05T14:31:21+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 new routing 2008-09-05T14:31:24+01:00 1366 Pratik Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Thanks for the feedback, guys. I made some edits to respond. I think this one is pretty close to final, unless someone else spots an area to improve. <div><p>Thanks for the feedback, guys. I made some edits to respond. I think this one is pretty close to final, unless someone else spots an area to improve.</p></div> false 2008-09-05T14:46:14+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 new routing 2008-09-05T14:46:16+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Pratik, there's already some guidance to avoid deeply-nested routes - see the section "Limits to Nesting". I'm a bit hesitant to link back to Jamis' article from here, since it predates the addition of :shallow to the routing code. But I could add a stronger warning if you think it's warranted. <div><p>Pratik, there's already some guidance to avoid deeply-nested routes - see the section "Limits to Nesting". I'm a bit hesitant to link back to Jamis' article from here, since it predates the addition of :shallow to the routing code. But I could add a stronger warning if you think it's warranted.</p></div> false 2008-09-05T14:48:44+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 new routing 2008-09-05T14:48:48+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 I think the :shallow option needs to be explained better. It took me a while to see what the :shallow option is doing, but after I understood what the option does, I wondered: "what's the point? how is this any different from not nesting the resources in the first place?" Only after reading Ryan's blog today (http://feeds.feedburner.com/~r/RyansScraps/~3/386049038/what-s-new-in-edge-rails-shallow-routes) did I understand its purpose: "No longer do you need to separately declare direct routes in addition to nested routes, the :shallow option automatically make all necessary routes." I think that an explanation similar to Ryan's is better. <div><p>I think the :shallow option needs to be explained better. It took me a while to see what the :shallow option is doing, but after I understood what the option does, I wondered: "what's the point? how is this any different from not nesting the resources in the first place?" Only after reading Ryan's blog today (<a href="http://feeds.feedburner.com/~r/RyansScraps/~3/386049038/what-s-new-in-edge-rails-shallow-routes)">http://feeds.feedburner.com/~r/R...</a> did I understand its purpose: "No longer do you need to separately declare direct routes in addition to nested routes, the :shallow option automatically make all necessary routes."</p> <p>I think that an explanation similar to Ryan's is better.</p></div> false 2008-09-08T12:06:26+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 new routing 2008-09-08T12:06:31+01:00 10679 Hongli Lai Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 I've reworked the section on nested and shallowed routes. <div><p>I've reworked the section on nested and shallowed routes.</p></div> false 2008-09-08T13:13:25+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 new routing 2008-09-08T13:13:31+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 This guide is pretty much done now. There are some typos "/magazines/1/ad/1" - it should be 'ads'. <div><p>This guide is pretty much done now. There are some typos "/magazines/1/ad/1" - it should be 'ads'.</p></div> false 2008-09-10T11:58:23+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 new routing 2008-09-10T11:58:31+01:00 1366 Pratik Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Yeah, it would help if we didn't show people the wrong URLs, wouldn't it? Thanks for catching that; I don't know where my brain was vacationing. Fixes committed. <div><p>Yeah, it would help if we didn't show people the wrong URLs, wouldn't it? Thanks for catching that; I don't know where my brain was vacationing. Fixes committed.</p></div> false 2008-09-10T12:55:58+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 new routing 2008-09-10T12:56:03+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Koz caught that ;-) Alright, we have our first guide that's "done" thanks to Mike. @Mike, could you please drop me an email to pratiknaik aT gmail so that we can sort out prizes and stuff. <div><p>Koz caught that ;-)</p> <p>Alright, we have our first guide that's "done" thanks to Mike.</p> <p>@Mike, could you please drop me an email to pratiknaik aT gmail so that we can sort out prizes and stuff.</p></div> true 2008-09-10T13:01:15+01:00 1366 --- :state: new 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved routing 2008-09-10T13:01:21+01:00 1366 Pratik Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Good job. :) Could you also add a description to the index page (index.txt)? And some final comments: "These default routes are automatically generated when you create a new Rails application. If you're using RESTful routing, you will probably want to remove them." I think you should say something along the lines of "you will probably want to remove them, if you don't use them". The current sentence might make the reader think that having just 1 REST route will make the default routes obsolete, either because of magic or because a REST route automatically creates default routes, or something. And: map.resources photos, ... Shouldn't "photos" be a string here? <div><p>Good job. :) Could you also add a description to the index page (index.txt)?</p> <p>And some final comments:</p> <p>"These default routes are automatically generated when you create a new Rails application. If you're using RESTful routing, you will probably want to remove them."</p> <p>I think you should say something along the lines of "you will probably want to remove them, if you don't use them". The current sentence might make the reader think that having just 1 REST route will make the default routes obsolete, either because of magic or because a REST route automatically creates default routes, or something.</p> <p>And:</p> <p>map.resources photos, ...</p> <p>Shouldn't "photos" be a string here?</p></div> true 2008-09-12T12:03:20+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved routing 2008-09-12T12:03:31+01:00 10679 Hongli Lai Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Thanks Hongli. I've done that big of cleanup. <div><p>Thanks Hongli. I've done that big of cleanup.</p></div> true 2008-09-13T13:00:30+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved routing 2008-09-13T13:00:55+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 OK. :) Just in case you didn't know, you can view your own work here: http://railsguides.phusion.nl/routing/routing_outside_in.html <div><p>OK. :) Just in case you didn't know, you can view your own work here: <a href="http://railsguides.phusion.nl/routing/routing_outside_in.html">http://railsguides.phusion.nl/ro...</a></p></div> true 2008-09-13T13:11:05+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved routing 2008-09-13T13:11:26+01:00 10679 Hongli Lai Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 OK. :) Just in case you didn't know, you can view your own work here: http://railsguides.phusion.nl/routing/routing_outside_in.html <div><p>OK. :) Just in case you didn't know, you can view your own work here: <a href="http://railsguides.phusion.nl/routing/routing_outside_in.html">http://railsguides.phusion.nl/ro...</a></p></div> true 2008-09-13T13:15:09+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved routing 2008-09-13T13:15:33+01:00 10679 Hongli Lai Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Excellent writeup. From my first glance it seems the 'map.namespace' is not mentioned - although that could have been intentional. <div><p>Excellent writeup. From my first glance it seems the 'map.namespace' is not mentioned - although that could have been intentional.</p></div> true 2008-09-16T21:27:57+01:00 1366 --- :tag: routing 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved routing 2008-09-16T21:27:59+01:00 32163 ronin-32163 (at lighthouseapp) Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 OOps .. for some reason Lighthouse just updated the tag. Sorry. <div><p>OOps .. for some reason Lighthouse just updated the tag. Sorry.</p></div> true 2008-09-16T21:28:52+01:00 1366 --- :tag: "[routing]" 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-16T21:28:58+01:00 32163 ronin-32163 (at lighthouseapp) Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Mike, great guide. Found it really useful as I'm new to rails. Just a couple of minor issues though: 1. Field "used for" in table in section 3.6 uses "photo" instead of "ad" in multiple places. 2. In section 4.2 there is <code>map.connect ':controller/:action/:id/:userid:</code>. The <code>:userid:</code> at the end should probably be <code>:user_id<code>. 3. In 4.9 a word "engulf" _could_ be replaced with some more common word that non-native English speakers, such as myself, would understand. Word "capture" comes to mind as a possible replacement. Though it is easy to understand what it means by reading a bit further. 4. In section 5.0 there is a <code>/photo/new/1.xml</code> as an example. Don't know if this is intentional or not, but according to my limited knowledge of Rails this example doesn't really make a lot of sense as you're passing an id to "new" action. Even though it is technically correct, perhaps a better example can be used if its not intentional. Thanks! <div><p>Mike, great guide. Found it really useful as I'm new to rails.</p> <p>Just a couple of minor issues though:</p> <ol> <li>Field "used for" in table in section 3.6 uses "photo" instead of "ad" in multiple places.</li> <li>In section 4.2 there is <code>map.connect ':controller/:action/:id/:userid:</code>. The <code>:userid:</code> at the end should probably be <code>:user_id</code>.</li> <li>In 4.9 a word "engulf" <em>could</em> be replaced with some more common word that non-native English speakers, such as myself, would understand. Word "capture" comes to mind as a possible replacement. Though it is easy to understand what it means by reading a bit further.</li> <li>In section 5.0 there is a <code>/photo/new/1.xml</code> as an example. Don't know if this is intentional or not, but according to my limited knowledge of Rails this example doesn't really make a lot of sense as you're passing an id to "new" action. Even though it is technically correct, perhaps a better example can be used if its not intentional.</li> </ol> <p>Thanks!</p></div> true 2008-09-18T00:45:24+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-18T00:45:26+01:00 718 Nemanja Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Thanks for the great feedback, Nemanja. I'll fix up those things in the next version (to be pushed later tonight). <div><p>Thanks for the great feedback, Nemanja. I'll fix up those things in the next version (to be pushed later tonight).</p></div> true 2008-09-18T01:33:37+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-18T01:33:38+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Mike, thanks for taking care of it so quickly. There is one thing that still confuses me though. In sections 4.2 and 4.3 there is <code>:user_id:</code> and <code>:userid:</code>. I am confused by that colon at the end. Is that just a typo or does it have some special meaning? <div><p>Mike, thanks for taking care of it so quickly. There is one thing that still confuses me though. In sections 4.2 and 4.3 there is <code>:user_id:</code> and <code>:userid:</code>. I am confused by that colon at the end. Is that just a typo or does it have some special meaning?</p></div> true 2008-09-18T09:47:47+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-18T09:47:49+01:00 718 Nemanja Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 It means I'm an idiot. :) Fixed. <div><p>It means I'm an idiot. :) Fixed.</p></div> true 2008-09-18T11:57:35+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-18T11:57:38+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Hi Mike In section 1.1, you give an example HTTP request `GET /patient/17` -- perhaps use the default resourceful `GET /patients/17`, with patients in plural? <div><p>Hi Mike</p> <p>In section 1.1, you give an example HTTP request <code>GET /patient/17</code> -- perhaps use the default resourceful <code>GET /patients/17</code>, with patients in plural?</p></div> true 2008-09-23T22:49:08+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-23T22:49:12+01:00 17949 Daniel Schierbeck Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Good point. I've made the change. <div><p>Good point. I've made the change.</p></div> true 2008-09-23T23:12:37+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-23T23:12:42+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Hi! A very good guide, I have found it really helpful. However I think I found a little typo error: In section 3.9. (Namespaced Resources) you write path_prefix twice in the last two examples: map.resources :tags, :path_prefix => 'admin_photo_', :path_prefix => 'admin/photos/:photo_id', :controller => 'admin/photo_tags' Doesn't it should be :name_prefix and :path_prefix? Maybe I'm wrong... <div><p>Hi! A very good guide, I have found it really helpful.</p> <p>However I think I found a little typo error: In section 3.9. (Namespaced Resources) you write path_prefix twice in the last two examples:</p> <p>map.resources :tags, :path_prefix =&gt; 'admin_photo_', :path_prefix =&gt; 'admin/photos/:photo_id', :controller =&gt; 'admin/photo_tags'</p> <p>Doesn't it should be :name_prefix and :path_prefix? Maybe I'm wrong...</p></div> true 2008-09-26T21:04:19+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-26T21:04:23+01:00 19122 Csiszár Attila Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Thanks Csiszár. I just pushed up that fix, along with some other minor changes. <div><p>Thanks Csisz&aacute;r. I just pushed up that fix, along with some other minor changes.</p></div> true 2008-09-27T02:36:50+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-27T02:36:55+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 In the section on singular resources, it says that map.resource creates 7 named routes and then proceeds to show a table with 6 routes. 7 should be changed to 6, no? <div><p>In the section on singular resources, it says that map.resource creates 7 named routes and then proceeds to show a table with 6 routes. 7 should be changed to 6, no?</p></div> true 2008-09-30T02:29:09+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-30T02:29:12+01:00 6372 Fabio Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Yes. Good catch. <div><p>Yes. Good catch.</p></div> true 2008-09-30T02:44:25+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-30T02:44:30+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Also, in section 3.7.7, just below the resource code, it says that a named route will be generated called "agency_photo_edit_path". I believe that should be "agency_edit_photo_path". Thank very much, by the way, for this doc. Great job. <div><p>Also, in section 3.7.7, just below the resource code, it says that a named route will be generated called "agency_photo_edit_path". I believe that should be "agency_edit_photo_path".</p> <p>Thank very much, by the way, for this doc. Great job.</p></div> true 2008-09-30T02:49:23+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-30T02:49:29+01:00 6372 Fabio Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Fixed, along with a couple of other route name mistakes. <div><p>Fixed, along with a couple of other route name mistakes.</p></div> true 2008-09-30T15:49:57+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-09-30T15:50:00+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 You could also mention about :namespace option, i found it useful for namespacing with subdomain_fu you can define these routes @@@ ruby map.with_options(:namespace => 'admin/', :conditions => { :subdomain => 'admin'}) do |admin| admin.root :controller => 'admin/blogs' admin.resources :categories, :blogs end @@@ instead of @@@ ruby map.with_options(:conditions => { :subdomain => 'admin'}) do |admin| admin.root :controller => 'admin/blogs' admin.resources :categories, :controller => 'admin/categories' admin.resources :blogs, :controller => 'admin/blogs' end @@@ unfortunately it only works with resources <div><p>You could also mention about :namespace option, i found it useful for namespacing with subdomain_fu</p> <p>you can define these routes</p> <pre><code class="ruby"> map.with_options(:namespace =&gt; 'admin/', :conditions =&gt; { :subdomain =&gt; 'admin'}) do |admin| admin.root :controller =&gt; 'admin/blogs' admin.resources :categories, :blogs end </code></pre> <p>instead of</p> <pre><code class="ruby"> map.with_options(:conditions =&gt; { :subdomain =&gt; 'admin'}) do |admin| admin.root :controller =&gt; 'admin/blogs' admin.resources :categories, :controller =&gt; 'admin/categories' admin.resources :blogs, :controller =&gt; 'admin/blogs' end </code></pre> <p>unfortunately it only works with resources</p></div> true 2008-10-04T18:42:17+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-10-04T18:42:21+01:00 17448 ronin Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Updated, along with a typo fix. <div><p>Updated, along with a typo fix.</p></div> true 2008-10-07T12:04:18+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-10-07T12:04:24+01:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 I believe this is a typo: >4.5. Defining Defaults >You do not need to explicitly use the :controller and :action symbols within a route. You can supply defaults for these two parameters in a hash: > map.connect 'photo/:id', :controller => 'photos', :action => 'show' >With this route, an incoming URL of /photos/12 would be dispatched to the show action within the Photos controller. Since the route is singular--"photo/:id"--then the plural url--"photos/12"--wouldn't (AFAIK) match. <div><p>I believe this is a typo:</p> <blockquote> <p>4.5. Defining Defaults</p> <p>You do not need to explicitly use the :controller and :action symbols within a route. You can supply defaults for these two parameters in a hash:</p> <p>map.connect 'photo/:id', :controller =&gt; 'photos', :action =&gt; 'show'</p> <p>With this route, an incoming URL of /photos/12 would be dispatched to the show action within the Photos controller.</p> </blockquote> <p>Since the route is singular--"photo/:id"--then the plural url--"photos/12"--wouldn't (AFAIK) match.</p></div> true 2008-11-09T06:25:12+00:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-11-09T06:25:13+00:00 28039 Brandon Zylstra Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 There's a typo in 7.1. Using map.root: map.index :controller => "pages", :action => "main" should be map.index '', :controller => "pages", :action => "main" <div><p>There's a typo in 7.1. Using map.root:</p> <p>map.index :controller =&gt; "pages", :action =&gt; "main"</p> <p>should be</p> <p>map.index '', :controller =&gt; "pages", :action =&gt; "main"</p></div> true 2008-11-24T14:32:53+00:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-11-24T14:32:56+00:00 38706 zoopzoop Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 1366 0 Thanks folks. Typo fixes will be committed today. <div><p>Thanks folks. Typo fixes will be committed today.</p></div> true 2008-11-30T13:01:00+00:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved 2008-11-30T13:01:04+00:00 7211 Mike Gunderloy Pratik Pratik http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 Some places you use @@@ map.with_options(:namespace => "admin") do |admin| @@@ while other places you use @@@ map.namespace(:admin) do |admin| @@@ For a new-comer like me, it's impossible to know what's best practice. Up until now I've used the latter method, but when reading this guide I was wondering if maybe with_options was better, but for generating namespaces only (without more options), the latter seems more convenient. <div><p>Some places you use</p> <pre><code> map.with_options(:namespace =&gt; &quot;admin&quot;) do |admin| </code></pre> <p>while other places you use</p> <pre><code> map.namespace(:admin) do |admin| </code></pre> <p>For a new-comer like me, it's impossible to know what's best practice. Up until now I've used the latter method, but when reading this guide I was wondering if maybe with_options was better, but for generating namespaces only (without more options), the latter seems more convenient.</p></div> true 2008-12-03T12:41:48+00:00 1366 --- :tag: :assigned_user: 1366 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved "best practice" namespaces routing 2008-12-03T12:41:51+00:00 18776 Peter Haza Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 The typo in 4.5 (singular route and plural url, as mentioned by Brandon) is still there. <div><p>The typo in 4.5 (singular route and plural url, as mentioned by Brandon) is still there.</p></div> true 2008-12-03T19:20:39+00:00 1366 --- :tag: "\"best practice\" namespaces routing" 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved defaults defining typo 2008-12-03T19:20:44+00:00 39689 Vegar Vikan Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 Vegar - Actually, the typo is fixed. There's just a delay between fixes in the source and updates to the online version. If you want to check, you need to look at the docrails project on github to be sure. <div><p>Vegar - Actually, the typo is fixed. There's just a delay between fixes in the source and updates to the online version. If you want to check, you need to look at the docrails project on github to be sure.</p></div> true 2008-12-04T14:26:09+00:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved defaults defining typo 2008-12-04T14:26:11+00:00 7211 Mike Gunderloy Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 In section 3.7 the last code example expect controller like "adminphotos", "adminvideos" and not "admin/photos" and "admin/videos". <div><p>In section 3.7 the last code example expect controller like "adminphotos", "adminvideos" and not "admin/photos" and "admin/videos".</p></div> true 2009-02-04T10:36:26+00:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 resolved defaults defining typo 2009-02-04T10:36:29+00:00 38165 venlix Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 Excellent guide, improved my understanding of routes a lot. I suggest you add another section in the "Inspecting and Testing Routes": 8.2 Debugging routes in IRB >> app.your_generator_path(@your, @generator) ...generates a nice path for you... >> rts = ActionController::Routing::Routes ; nil => nil (; nil to suppress the visual diarrhea) >> rts.generate_path({:controller => :generator}) ... more verbose way to do what the generators do... >> rts.recognize_path("/your/path/here") ...works... >> rts.recognize_path("/your/path/here?some=argument") ...doesn't... This information is out there, but scattered. The "app.your_generator_path" tip is huge, and was difficult to unearth. Also, if you know about techniques to directly inspect the RouteSet, that would be really helpful. As I was coming up to speed on this stuff, it was very frustrating trying to figure out why things wouldn't generate. <div><p>Excellent guide, improved my understanding of routes a lot. I suggest you add another section in the "Inspecting and Testing Routes":</p> <p>8.2 Debugging routes in IRB</p> <blockquote> <blockquote> <p>app.your_generator_path(@your, @generator) ...generates a nice path for you...</p> <p>rts = ActionController::Routing::Routes ; nil =&gt; nil (; nil to suppress the visual diarrhea)</p> <p>rts.generate_path({:controller =&gt; :generator}) ... more verbose way to do what the generators do...</p> <p>rts.recognize_path("/your/path/here") ...works... rts.recognize_path("/your/path/here?some=argument") ...doesn't...</p> </blockquote> </blockquote> <p>This information is out there, but scattered. The "app.your_generator_path" tip is huge, and was difficult to unearth.</p> <p>Also, if you know about techniques to directly inspect the RouteSet, that would be really helpful. As I was coming up to speed on this stuff, it was very frustrating trying to figure out why things wouldn't generate.</p></div> true 2009-03-25T01:00:31+00:00 1366 --- :state: resolved 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 defaults defining typo 2009-03-25T01:00:32+00:00 32839 dondo (at dondo) Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 I would suggest two changes to this outstanding document. First, the initial metaphor feels a little clunky (though better than pigs -> sausage ;-). I am thinking more along the lines of street address to driving directions, which has the advantage of being directly related to a different kind of routing. Personal taste, though. Second, in the section on Testing, in addition to explaining the assertions, you should also at least outline _where_ these tests ought to go (unit, functional, integration, etc.), and probably include a link to the appropriate section of the Testing Guide, http://guides.rubyonrails.org/testing.html, for more details. <div><p>I would suggest two changes to this outstanding document. First, the initial metaphor feels a little clunky (though better than pigs -&gt; sausage ;-). I am thinking more along the lines of street address to driving directions, which has the advantage of being directly related to a different kind of routing. Personal taste, though.</p> <p>Second, in the section on Testing, in addition to explaining the assertions, you should also at least outline <em>where</em> these tests ought to go (unit, functional, integration, etc.), and probably include a link to the appropriate section of the Testing Guide, <a href= "http://guides.rubyonrails.org/testing.html">http://guides.rubyonrails.org/testing.html</a>, for more details.</p></div> true 2009-05-14T20:35:35+01:00 1366 --- :tag: defaults defining typo 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 testing 2009-05-14T20:35:38+01:00 17425 Alderete Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 Gah. The Lighthouse comments form tags field should be additive, not replace all existing tags. Make deleting tags from a ticket a separate action. Sorry! <div><p>Gah. The Lighthouse comments form tags field should be additive, not replace all existing tags. Make deleting tags from a ticket a separate action. Sorry!</p></div> true 2009-05-14T20:37:19+01:00 1366 --- :tag: testing 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 defaults defining testing typo 2009-05-14T20:37:23+01:00 17425 Alderete Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 I presume the period at the end of the blue code block in section 3.8 is a typo <div><p>I presume the period at the end of the blue code block in section 3.8 is a typo</p></div> true 2009-07-02T12:40:48+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 defaults defining testing typo 2009-07-02T12:40:52+01:00 58644 steven_noble Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 Yeah, it is kind of inline code displayed in its own line... I've removed the period, it's not obvios so it may confuse. Thanks! <div><p>Yeah, it is kind of inline code displayed in its own line... I've removed the period, it's not obvios so it may confuse.</p> <p>Thanks!</p></div> false 2009-07-02T13:55:33+01:00 1366 --- :state: 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 available defaults defining testing typo 2009-07-02T13:55:36+01:00 11378 Xavier Noria Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 true 2009-07-02T13:56:56+01:00 1366 --- :state: available 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 published defaults defining testing typo 2009-07-02T13:57:00+01:00 11378 Xavier Noria Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 This, in the testing routes section: assert_routing { :path => "photos", :method => :post }, { :controller => "photos", :action => "create" } gives me a syntax error (ruby 1.8.6 (2008-03-03 patchlevel 114)). Adding the parentheses around the method call solves it: assert_routing({ :path => "photos", :method => :post }, { :controller => "photos", :action => "create" }) <div><p>This, in the testing routes section:</p> <p>assert_routing { :path =&gt; "photos", :method =&gt; :post }, { :controller =&gt; "photos", :action =&gt; "create" }</p> <p>gives me a syntax error (ruby 1.8.6 (2008-03-03 patchlevel 114)).</p> <p>Adding the parentheses around the method call solves it:</p> <p>assert_routing({ :path =&gt; "photos", :method =&gt; :post }, { :controller =&gt; "photos", :action =&gt; "create" })</p></div> true 2009-08-28T15:45:54+01:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 published defaults defining testing typo 2009-08-28T15:46:02+01:00 38831 Balint Erdi Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 There seems to be conflict between sections 3.7.0 and 3.10 (looks like they try to explain the same thing but in different ways). The first gives you the impression that you can create an admin section with "map.with_options" but it didn't work for me at all. 3.10 uses "map.namespace" and seems to work well. If you're reading top to bottom, and you're a moron like me, you get stumped until you try the example from 3.10. <div><p>There seems to be conflict between sections 3.7.0 and 3.10 (looks like they try to explain the same thing but in different ways). The first gives you the impression that you can create an admin section with "map.with_options" but it didn't work for me at all. 3.10 uses "map.namespace" and seems to work well. If you're reading top to bottom, and you're a moron like me, you get stumped until you try the example from 3.10.</p></div> true 2009-09-29T06:45:39+01:00 1366 --- :tag: defaults defining testing typo 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 published routes routing 2009-09-29T06:45:45+01:00 71374 hayesr Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 for the last part of the fuide "8.2 Testing Routes" it may help beginners to get some tip where to test the routes, eg. in "integration" or "functional" (since I'm using RSpec, I would place it in the controller section of the specs. <div><p>for the last part of the fuide "8.2 Testing Routes" it may help beginners to get some tip where to test the routes, eg. in "integration" or "functional"<br> (since I'm using RSpec, I would place it in the controller section of the specs.</p></div> true 2009-10-18T22:42:35+01:00 1366 --- :tag: routes routing 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 published routes routing testing 2009-10-18T22:42:38+01:00 73572 thorsten Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 Section 2.5 has an id of "regular-routes". Section 4 also has an id of "regular-routes". This is not valid, but that's not really the issue. More troublesome is that when I click the table of contents item for Section 4, the browser takes me to section 2.5, the first instance of the id "regular-routes", rather than to Section 4, where I want to navigate to. This happens in Safari 4 and Firefox 3.5. These two sections should have different IDs. <div><p>Section 2.5 has an id of "regular-routes". Section 4 also has an id of "regular-routes". This is not valid, but that's not really the issue. More troublesome is that when I click the table of contents item for Section 4, the browser takes me to section 2.5, the first instance of the id "regular-routes", rather than to Section 4, where I want to navigate to. This happens in Safari 4 and Firefox 3.5. These two sections should have different IDs.</p></div> true 2009-12-08T15:42:15+00:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 published routes routing testing 2009-12-08T15:42:21+00:00 34401 Alex Kahn Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 @Alex, that's right. These IDs are generated in an automatic manner and such a collision should be detected. Thanks for the comment. <div><p>@Alex, that's right. These IDs are generated in an automatic manner and such a collision should be detected. Thanks for the comment.</p></div> true 2009-12-08T18:27:02+00:00 1366 --- {} 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 published routes routing testing 2009-12-08T18:27:05+00:00 11378 Xavier Noria Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3 7211 0 hi, --> 4.9 Route Glogging map.connect ... :action => 'unknown', <-- the little thing with big effekt! psi <div><p>hi,</p> <p>--&gt; 4.9 Route Glogging map.connect ... :action =&gt; 'unknown', &lt;-- the little thing with big effekt!</p> <p>psi</p></div> true 2010-01-24T16:58:16+00:00 1366 --- :tag: routes routing testing 3 routing-from-the-outside-in-cover-the-user-facing-features-of-routing 0 16213 published 2010-01-24T16:58:18+00:00 83786 psi Pratik Mike Gunderloy http://rails.lighthouseapp.com/projects/16213/tickets/3