mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
Use ruby 1.9 lambda syntax in documentations [ci skip]
This commit is contained in:
parent
76836ef7db
commit
e4dd700b5d
4 changed files with 7 additions and 7 deletions
|
@ -16,7 +16,7 @@ module ActionDispatch
|
|||
# env["action_dispatch.parameter_filter"] = [:foo, "bar"]
|
||||
# => replaces the value to all keys matching /foo|bar/i with "[FILTERED]"
|
||||
#
|
||||
# env["action_dispatch.parameter_filter"] = lambda do |k,v|
|
||||
# env["action_dispatch.parameter_filter"] = -> (k, v) do
|
||||
# v.reverse! if k =~ /secret/i
|
||||
# end
|
||||
# => reverses the value to all keys matching /secret/i
|
||||
|
|
|
@ -11,9 +11,9 @@ module ActionDispatch
|
|||
# the response body. This is important for streaming responses such as the
|
||||
# following:
|
||||
#
|
||||
# self.response_body = lambda { |response, output|
|
||||
# self.response_body = -> (response, output) do
|
||||
# # code here which refers to application models
|
||||
# }
|
||||
# end
|
||||
#
|
||||
# Cleanup callbacks will not be called until after the response_body lambda
|
||||
# is evaluated, ensuring that it can refer to application models and other
|
||||
|
|
|
@ -418,7 +418,7 @@ module ActionDispatch
|
|||
# A pattern can also point to a +Rack+ endpoint i.e. anything that
|
||||
# responds to +call+:
|
||||
#
|
||||
# match 'photos/:id', to: lambda {|hash| [200, {}, ["Coming soon"]] }, via: :get
|
||||
# match 'photos/:id', to: -> (hash) { [200, {}, ["Coming soon"]] }, via: :get
|
||||
# match 'photos/:id', to: PhotoRackApp, via: :get
|
||||
# # Yes, controller actions are just rack endpoints
|
||||
# match 'photos/:id', to: PhotosController.action(:show), via: :get
|
||||
|
@ -470,7 +470,7 @@ module ActionDispatch
|
|||
# +call+ or a string representing a controller's action.
|
||||
#
|
||||
# match 'path', to: 'controller#action', via: :get
|
||||
# match 'path', to: lambda { |env| [200, {}, ["Success!"]] }, via: :get
|
||||
# match 'path', to: -> (env) { [200, {}, ["Success!"]] }, via: :get
|
||||
# match 'path', to: RackApp, via: :get
|
||||
#
|
||||
# [:on]
|
||||
|
@ -899,7 +899,7 @@ module ActionDispatch
|
|||
#
|
||||
# Requests to routes can be constrained based on specific criteria:
|
||||
#
|
||||
# constraints(lambda { |req| req.env["HTTP_USER_AGENT"] =~ /iPhone/ }) do
|
||||
# constraints(-> (req) { req.env["HTTP_USER_AGENT"] =~ /iPhone/ }) do
|
||||
# resources :iphones
|
||||
# end
|
||||
#
|
||||
|
|
|
@ -80,7 +80,7 @@ module ActionView
|
|||
#
|
||||
# When used with the <tt>collection_select</tt> helper, <tt>:disabled</tt> can also be a Proc that identifies those options that should be disabled.
|
||||
#
|
||||
# collection_select(:post, :category_id, Category.all, :id, :name, {disabled: lambda{|category| category.archived? }})
|
||||
# collection_select(:post, :category_id, Category.all, :id, :name, {disabled: -> (category) { category.archived? }})
|
||||
#
|
||||
# If the categories "2008 stuff" and "Christmas" return true when the method <tt>archived?</tt> is called, this would return:
|
||||
# <select name="post[category_id]" id="post_category_id">
|
||||
|
|
Loading…
Reference in a new issue