From 3a48b83e5eec62a5d2bfab1a118c24b45345388c Mon Sep 17 00:00:00 2001 From: Andrew White Date: Sun, 5 Jan 2014 19:58:04 +0000 Subject: Allow an absolute controller path inside a module scope Fixes #12777 --- guides/source/routing.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'guides/source') diff --git a/guides/source/routing.md b/guides/source/routing.md index 3375293b5a..70d4722068 100644 --- a/guides/source/routing.md +++ b/guides/source/routing.md @@ -239,6 +239,8 @@ In each of these cases, the named routes remain the same as if you did not use ` | PATCH/PUT | /admin/posts/:id | posts#update | post_path(:id) | | DELETE | /admin/posts/:id | posts#destroy | post_path(:id) | +TIP: _If you need to use a different controller namespace inside a `namespace` block you can specify an absolute controller path, e.g: `get '/foo' => '/foo#index'`._ + ### Nested Resources It's common to have resources that are logically children of other resources. For example, suppose your application includes these models: -- cgit v1.2.3