From 1439a5423615f38461b87027db097098a8a5afbc Mon Sep 17 00:00:00 2001 From: Avneet Singh Malhotra Date: Mon, 26 Feb 2018 19:20:31 +0530 Subject: Correct `to` option's value of the route in the Bound Parameters section in routing guide. --- guides/source/routing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'guides/source/routing.md') diff --git a/guides/source/routing.md b/guides/source/routing.md index efc0e32b56..1e75cbf362 100644 --- a/guides/source/routing.md +++ b/guides/source/routing.md @@ -549,7 +549,7 @@ In particular, simple routing makes it very easy to map legacy URLs to new Rails When you set up a regular route, you supply a series of symbols that Rails maps to parts of an incoming HTTP request. For example, consider this route: ```ruby -get 'photos(/:id)', to: :display +get 'photos(/:id)', to: 'photos#display' ``` If an incoming request of `/photos/1` is processed by this route (because it hasn't matched any previous route in the file), then the result will be to invoke the `display` action of the `PhotosController`, and to make the final parameter `"1"` available as `params[:id]`. This route will also route the incoming request of `/photos` to `PhotosController#display`, since `:id` is an optional parameter, denoted by parentheses. -- cgit v1.2.3