From 3fccecb87b04cd550713ebf5d735c2a6dbccb4a1 Mon Sep 17 00:00:00 2001
From: the-undefined <joe.james@alliants.com>
Date: Fri, 13 Nov 2015 07:10:32 +0000
Subject: [ci skip] add `controller:` argument to routing.md

Passing a `Symbol` to the `to:` argument for a `get` route requires a `controller` argument to also be defined.
The documentation is missing the `controller:` argument, which leaving out raises a routing exception:

```ruby
get 'profile', to: :show
```

```
$ rake routes
ArgumentError: Missing :controller key on routes definition, please check your routes.
```

Adding the `controller:` argument maps the route correctly:

```ruby
get 'profile', to: :show, controller: 'users'
```
```
$ rake routes
profile GET    /profile(.:format)  users#show
```
---
 guides/source/routing.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'guides')

diff --git a/guides/source/routing.md b/guides/source/routing.md
index e4799d93fa..b8dd089753 100644
--- a/guides/source/routing.md
+++ b/guides/source/routing.md
@@ -142,10 +142,10 @@ Sometimes, you have a resource that clients always look up without referencing a
 get 'profile', to: 'users#show'
 ```
 
-Passing a `String` to `get` will expect a `controller#action` format, while passing a `Symbol` will map directly to an action:
+Passing a `String` to `get` will expect a `controller#action` format, while passing a `Symbol` will map directly to an action but you must also specify the `controller:` to use:
 
 ```ruby
-get 'profile', to: :show
+get 'profile', to: :show, controller: 'users'
 ```
 
 This resourceful route:
-- 
cgit v1.2.3