From fae17243984965b152d8212be6405ce840887018 Mon Sep 17 00:00:00 2001 From: "yuuji.yaginuma" Date: Wed, 3 Feb 2016 08:16:18 +0900 Subject: use rails command in routes task For other task has become to use the rails command at doc and test, I think that routes task also it is better to use the rails command. --- guides/source/routing.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'guides/source/routing.md') diff --git a/guides/source/routing.md b/guides/source/routing.md index d9e64d56ac..777d1d24b6 100644 --- a/guides/source/routing.md +++ b/guides/source/routing.md @@ -1139,18 +1139,18 @@ edit_user GET /users/:id/edit(.:format) users#edit You can search through your routes with the --grep option (-g for short). This outputs any routes that partially match the URL helper method name, the HTTP verb, or the URL path. ``` -$ bin/rake routes --grep new_comment -$ bin/rake routes -g POST -$ bin/rake routes -g admin +$ bin/rails routes --grep new_comment +$ bin/rails routes -g POST +$ bin/rails routes -g admin ``` If you only want to see the routes that map to a specific controller, there's the --controller option (-c for short). ``` -$ bin/rake routes --controller users -$ bin/rake routes --controller admin/users -$ bin/rake routes -c Comments -$ bin/rake routes -c Articles::CommentsController +$ bin/rails routes --controller users +$ bin/rails routes --controller admin/users +$ bin/rails routes -c Comments +$ bin/rails routes -c Articles::CommentsController ``` TIP: You'll find that the output from `rails routes` is much more readable if you widen your terminal window until the output lines don't wrap. -- cgit v1.2.3