TEST_CODEOWNERS/rails
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Improve guides note about using a proc/lambda as a route endpoint

Browse Source 
[ci skip]
This commit is contained in:
Carlos Antonio da Silva 2021-05-21 11:55:54 -03:00
parent e848e8861d
commit f7b65ee0c4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
guides/source/routing.md
View File

@ -920,7 +920,7 @@ As long as `MyRackApp` responds to `call` and returns a `[status, headers, body]
NOTE: For the curious, `'articles#index'` actually expands out to `ArticlesController.action(:index)`, which returns a valid Rack application.
NOTE: Since procs/lambdas are objects that happen to respond to `call` you can implement very simple routes (e.g. for health checks) inline:<br>`get '/health', to: ->(env) { [204, {}, ''] }`
NOTE: Since procs/lambdas are objects that respond to `call`, you can implement very simple routes (e.g. for health checks) inline:<br>`get '/health', to: ->(env) { [204, {}, ['']] }`
If you specify a Rack application as the endpoint for a matcher, remember that
the route will be unchanged in the receiving application. With the following