From eaf67ca9c3fbe3e45c8096ea7ffbde562ebfb76d Mon Sep 17 00:00:00 2001
From: Ryan Bigg <radarlistener@gmail.com>
Date: Fri, 31 Dec 2010 17:38:04 +1000
Subject: [PATCH] Routing guide: improve documentation for the scope method,
 demonstrating use of named parameters

---
 railties/guides/source/routing.textile | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/railties/guides/source/routing.textile b/railties/guides/source/routing.textile
index 15b26d8f9e..fda5c6c668 100644
--- a/railties/guides/source/routing.textile
+++ b/railties/guides/source/routing.textile
@@ -200,6 +200,16 @@ or, for a single case
 resources :posts, :path => "/admin/posts"
 </ruby>
 
+You can even set named parameters for the paths:
+
+<ruby>
+scope ":username" do
+  resources :posts
+end
+</ruby>
+
+This will provide you with URLs such as +/bob/posts/1+ and will allow you to reference the +username+ part of the path as +params[:username]+ in controllers, helpers and views.
+
 In each of these cases, the named routes remain the same as if you did not use +scope+. In the last case, the following paths map to +PostsController+:
 
 |_.HTTP Verb |_.Path               |_.action |_.named helper      |