actionpack 7.1.3.4 → 7.2.0.beta1

data/lib/action_controller/metal/mime_responds.rb

@@ -1,203 +1,213 @@
 # frozen_string_literal: true
 
+# :markup: markdown
+
 require "abstract_controller/collector"
 
 module ActionController # :nodoc:
   module MimeResponds
-    # Without web-service support, an action which collects the data for displaying a list of people
-    # might look something like this:
+    # Without web-service support, an action which collects the data for displaying
+    # a list of people might look something like this:
     #
-    #   def index
-    #     @people = Person.all
-    #   end
+    #     def index
+    #       @people = Person.all
+    #     end
     #
-    # That action implicitly responds to all formats, but formats can also be explicitly enumerated:
+    # That action implicitly responds to all formats, but formats can also be
+    # explicitly enumerated:
     #
-    #   def index
-    #     @people = Person.all
-    #     respond_to :html, :js
-    #   end
+    #     def index
+    #       @people = Person.all
+    #       respond_to :html, :js
+    #     end
     #
     # Here's the same action, with web-service support baked in:
     #
-    #   def index
-    #     @people = Person.all
+    #     def index
+    #       @people = Person.all
     #
-    #     respond_to do |format|
-    #       format.html
-    #       format.js
-    #       format.xml { render xml: @people }
+    #       respond_to do |format|
+    #         format.html
+    #         format.js
+    #         format.xml { render xml: @people }
+    #       end
     #     end
-    #   end
     #
-    # What that says is, "if the client wants HTML or JS in response to this action, just respond as we
-    # would have before, but if the client wants XML, return them the list of people in XML format."
-    # (\Rails determines the desired response format from the HTTP Accept header submitted by the client.)
+    # What that says is, "if the client wants HTML or JS in response to this action,
+    # just respond as we would have before, but if the client wants XML, return them
+    # the list of people in XML format." (Rails determines the desired response
+    # format from the HTTP Accept header submitted by the client.)
     #
-    # Supposing you have an action that adds a new person, optionally creating their company
-    # (by name) if it does not already exist, without web-services, it might look like this:
+    # Supposing you have an action that adds a new person, optionally creating their
+    # company (by name) if it does not already exist, without web-services, it might
+    # look like this:
     #
-    #   def create
-    #     @company = Company.find_or_create_by(name: params[:company][:name])
-    #     @person  = @company.people.create(params[:person])
+    #     def create
+    #       @company = Company.find_or_create_by(name: params[:company][:name])
+    #       @person  = @company.people.create(params[:person])
     #
-    #     redirect_to(person_list_url)
-    #   end
+    #       redirect_to(person_list_url)
+    #     end
     #
     # Here's the same action, with web-service support baked in:
     #
-    #   def create
-    #     company  = params[:person].delete(:company)
-    #     @company = Company.find_or_create_by(name: company[:name])
-    #     @person  = @company.people.create(params[:person])
+    #     def create
+    #       company  = params[:person].delete(:company)
+    #       @company = Company.find_or_create_by(name: company[:name])
+    #       @person  = @company.people.create(params[:person])
     #
-    #     respond_to do |format|
-    #       format.html { redirect_to(person_list_url) }
-    #       format.js
-    #       format.xml  { render xml: @person.to_xml(include: @company) }
+    #       respond_to do |format|
+    #         format.html { redirect_to(person_list_url) }
+    #         format.js
+    #         format.xml  { render xml: @person.to_xml(include: @company) }
+    #       end
     #     end
-    #   end
     #
-    # If the client wants HTML, we just redirect them back to the person list. If they want JavaScript,
-    # then it is an Ajax request and we render the JavaScript template associated with this action.
-    # Lastly, if the client wants XML, we render the created person as XML, but with a twist: we also
-    # include the person's company in the rendered XML, so you get something like this:
+    # If the client wants HTML, we just redirect them back to the person list. If
+    # they want JavaScript, then it is an Ajax request and we render the JavaScript
+    # template associated with this action. Lastly, if the client wants XML, we
+    # render the created person as XML, but with a twist: we also include the
+    # person's company in the rendered XML, so you get something like this:
     #
-    #   <person>
-    #     <id>...</id>
-    #     ...
-    #     <company>
+    #     <person>
     #       <id>...</id>
-    #       <name>...</name>
     #       ...
-    #     </company>
-    #   </person>
+    #       <company>
+    #         <id>...</id>
+    #         <name>...</name>
+    #         ...
+    #       </company>
+    #     </person>
     #
     # Note, however, the extra bit at the top of that action:
     #
-    #   company  = params[:person].delete(:company)
-    #   @company = Company.find_or_create_by(name: company[:name])
+    #     company  = params[:person].delete(:company)
+    #     @company = Company.find_or_create_by(name: company[:name])
     #
-    # This is because the incoming XML document (if a web-service request is in process) can only contain a
-    # single root-node. So, we have to rearrange things so that the request looks like this (url-encoded):
+    # This is because the incoming XML document (if a web-service request is in
+    # process) can only contain a single root-node. So, we have to rearrange things
+    # so that the request looks like this (url-encoded):
     #
-    #   person[name]=...&person[company][name]=...&...
+    #     person[name]=...&person[company][name]=...&...
     #
     # And, like this (xml-encoded):
     #
-    #   <person>
-    #     <name>...</name>
-    #     <company>
+    #     <person>
     #       <name>...</name>
-    #     </company>
-    #   </person>
+    #       <company>
+    #         <name>...</name>
+    #       </company>
+    #     </person>
     #
-    # In other words, we make the request so that it operates on a single entity's person. Then, in the action,
-    # we extract the company data from the request, find or create the company, and then create the new person
-    # with the remaining data.
+    # In other words, we make the request so that it operates on a single entity's
+    # person. Then, in the action, we extract the company data from the request,
+    # find or create the company, and then create the new person with the remaining
+    # data.
     #
-    # Note that you can define your own XML parameter parser which would allow you to describe multiple entities
-    # in a single request (i.e., by wrapping them all in a single root node), but if you just go with the flow
-    # and accept \Rails' defaults, life will be much easier.
+    # Note that you can define your own XML parameter parser which would allow you
+    # to describe multiple entities in a single request (i.e., by wrapping them all
+    # in a single root node), but if you just go with the flow and accept Rails'
+    # defaults, life will be much easier.
     #
-    # If you need to use a MIME type which isn't supported by default, you can register your own handlers in
-    # +config/initializers/mime_types.rb+ as follows.
+    # If you need to use a MIME type which isn't supported by default, you can
+    # register your own handlers in `config/initializers/mime_types.rb` as follows.
     #
-    #   Mime::Type.register "image/jpeg", :jpg
+    #     Mime::Type.register "image/jpeg", :jpg
     #
-    # +respond_to+ also allows you to specify a common block for different formats by using +any+:
+    # `respond_to` also allows you to specify a common block for different formats
+    # by using `any`:
     #
-    #   def index
-    #     @people = Person.all
+    #     def index
+    #       @people = Person.all
     #
-    #     respond_to do |format|
-    #       format.html
-    #       format.any(:xml, :json) { render request.format.to_sym => @people }
+    #       respond_to do |format|
+    #         format.html
+    #         format.any(:xml, :json) { render request.format.to_sym => @people }
+    #       end
     #     end
-    #   end
     #
     # In the example above, if the format is xml, it will render:
     #
-    #   render xml: @people
+    #     render xml: @people
     #
     # Or if the format is json:
     #
-    #   render json: @people
+    #     render json: @people
     #
-    # +any+ can also be used with no arguments, in which case it will be used for any format requested by
-    # the user:
+    # `any` can also be used with no arguments, in which case it will be used for
+    # any format requested by the user:
     #
-    #   respond_to do |format|
-    #     format.html
-    #     format.any { redirect_to support_path }
-    #   end
+    #     respond_to do |format|
+    #       format.html
+    #       format.any { redirect_to support_path }
+    #     end
     #
     # Formats can have different variants.
     #
-    # The request variant is a specialization of the request format, like <tt>:tablet</tt>,
-    # <tt>:phone</tt>, or <tt>:desktop</tt>.
+    # The request variant is a specialization of the request format, like `:tablet`,
+    # `:phone`, or `:desktop`.
     #
-    # We often want to render different html/json/xml templates for phones,
-    # tablets, and desktop browsers. Variants make it easy.
+    # We often want to render different html/json/xml templates for phones, tablets,
+    # and desktop browsers. Variants make it easy.
     #
-    # You can set the variant in a +before_action+:
+    # You can set the variant in a `before_action`:
     #
-    #   request.variant = :tablet if /iPad/.match?(request.user_agent)
+    #     request.variant = :tablet if /iPad/.match?(request.user_agent)
     #
     # Respond to variants in the action just like you respond to formats:
     #
-    #   respond_to do |format|
-    #     format.html do |variant|
-    #       variant.tablet # renders app/views/projects/show.html+tablet.erb
-    #       variant.phone { extra_setup; render ... }
-    #       variant.none  { special_setup } # executed only if there is no variant set
+    #     respond_to do |format|
+    #       format.html do |variant|
+    #         variant.tablet # renders app/views/projects/show.html+tablet.erb
+    #         variant.phone { extra_setup; render ... }
+    #         variant.none  { special_setup } # executed only if there is no variant set
+    #       end
     #     end
-    #   end
     #
     # Provide separate templates for each format and variant:
     #
-    #   app/views/projects/show.html.erb
-    #   app/views/projects/show.html+tablet.erb
-    #   app/views/projects/show.html+phone.erb
+    #     app/views/projects/show.html.erb
+    #     app/views/projects/show.html+tablet.erb
+    #     app/views/projects/show.html+phone.erb
     #
-    # When you're not sharing any code within the format, you can simplify defining variants
-    # using the inline syntax:
+    # When you're not sharing any code within the format, you can simplify defining
+    # variants using the inline syntax:
     #
-    #   respond_to do |format|
-    #     format.js         { render "trash" }
-    #     format.html.phone { redirect_to progress_path }
-    #     format.html.none  { render "trash" }
-    #   end
+    #     respond_to do |format|
+    #       format.js         { render "trash" }
+    #       format.html.phone { redirect_to progress_path }
+    #       format.html.none  { render "trash" }
+    #     end
     #
-    # Variants also support common +any+/+all+ block that formats have.
+    # Variants also support common `any`/`all` block that formats have.
     #
     # It works for both inline:
     #
-    #   respond_to do |format|
-    #     format.html.any   { render html: "any"   }
-    #     format.html.phone { render html: "phone" }
-    #   end
+    #     respond_to do |format|
+    #       format.html.any   { render html: "any"   }
+    #       format.html.phone { render html: "phone" }
+    #     end
     #
     # and block syntax:
     #
-    #   respond_to do |format|
-    #     format.html do |variant|
-    #       variant.any(:tablet, :phablet){ render html: "any" }
-    #       variant.phone { render html: "phone" }
+    #     respond_to do |format|
+    #       format.html do |variant|
+    #         variant.any(:tablet, :phablet){ render html: "any" }
+    #         variant.phone { render html: "phone" }
+    #       end
     #     end
-    #   end
     #
     # You can also set an array of variants:
     #
-    #   request.variant = [:tablet, :phone]
+    #     request.variant = [:tablet, :phone]
     #
-    # This will work similarly to formats and MIME types negotiation. If there
-    # is no +:tablet+ variant declared, the +:phone+ variant will be used:
+    # This will work similarly to formats and MIME types negotiation. If there is no
+    # `:tablet` variant declared, the `:phone` variant will be used:
     #
-    #   respond_to do |format|
-    #     format.html.none
-    #     format.html.phone # this gets rendered
-    #   end
+    #     respond_to do |format|
+    #       format.html.none
+    #       format.html.phone # this gets rendered
+    #     end
     def respond_to(*mimes)
       raise ArgumentError, "respond_to takes either types or a block, never both" if mimes.any? && block_given?
 
@@ -217,27 +227,26 @@ module ActionController # :nodoc:
       end
     end
 
-    # A container for responses available from the current controller for
-    # requests for different mime-types sent to a particular action.
-    #
-    # The public controller methods +respond_to+ may be called with a block
-    # that is used to define responses to different mime-types, e.g.
-    # for +respond_to+ :
-    #
-    #   respond_to do |format|
-    #     format.html
-    #     format.xml { render xml: @people }
-    #   end
-    #
-    # In this usage, the argument passed to the block (+format+ above) is an
-    # instance of the ActionController::MimeResponds::Collector class. This
-    # object serves as a container in which available responses can be stored by
-    # calling any of the dynamically generated, mime-type-specific methods such
-    # as +html+, +xml+ etc on the Collector. Each response is represented by a
-    # corresponding block if present.
-    #
-    # A subsequent call to #negotiate_format(request) will enable the Collector
-    # to determine which specific mime-type it should respond with for the current
+    # A container for responses available from the current controller for requests
+    # for different mime-types sent to a particular action.
+    #
+    # The public controller methods `respond_to` may be called with a block that is
+    # used to define responses to different mime-types, e.g. for `respond_to` :
+    #
+    #     respond_to do |format|
+    #       format.html
+    #       format.xml { render xml: @people }
+    #     end
+    #
+    # In this usage, the argument passed to the block (`format` above) is an
+    # instance of the ActionController::MimeResponds::Collector class. This object
+    # serves as a container in which available responses can be stored by calling
+    # any of the dynamically generated, mime-type-specific methods such as `html`,
+    # `xml` etc on the Collector. Each response is represented by a corresponding
+    # block if present.
+    #
+    # A subsequent call to #negotiate_format(request) will enable the Collector to
+    # determine which specific mime-type it should respond with for the current
     # request, with this response then being accessible by calling #response.
     class Collector
       include AbstractController::Collector
@@ -306,7 +315,7 @@ module ActionController # :nodoc:
         end
         alias :all :any
 
-        def method_missing(name, *args, &block)
+        def method_missing(name, *, &block)
           @variants[name] = block if block_given?
         end
 

data/lib/action_controller/metal/parameter_encoding.rb

@@ -1,5 +1,7 @@
 # frozen_string_literal: true
 
+# :markup: markdown
+
 module ActionController
   # Specify binary encoding for parameters for a given action.
   module ParameterEncoding
@@ -21,59 +23,59 @@ module ActionController
         end
       end
 
-      # Specify that a given action's parameters should all be encoded as
-      # ASCII-8BIT (it "skips" the encoding default of UTF-8).
+      # Specify that a given action's parameters should all be encoded as ASCII-8BIT
+      # (it "skips" the encoding default of UTF-8).
       #
       # For example, a controller would use it like this:
       #
-      #   class RepositoryController < ActionController::Base
-      #     skip_parameter_encoding :show
+      #     class RepositoryController < ActionController::Base
+      #       skip_parameter_encoding :show
       #
-      #     def show
-      #       @repo = Repository.find_by_filesystem_path params[:file_path]
+      #       def show
+      #         @repo = Repository.find_by_filesystem_path params[:file_path]
       #
-      #       # `repo_name` is guaranteed to be UTF-8, but was ASCII-8BIT, so
-      #       # tag it as such
-      #       @repo_name = params[:repo_name].force_encoding 'UTF-8'
-      #     end
+      #         # `repo_name` is guaranteed to be UTF-8, but was ASCII-8BIT, so
+      #         # tag it as such
+      #         @repo_name = params[:repo_name].force_encoding 'UTF-8'
+      #       end
       #
-      #     def index
-      #       @repositories = Repository.all
+      #       def index
+      #         @repositories = Repository.all
+      #       end
       #     end
-      #   end
       #
       # The show action in the above controller would have all parameter values
-      # encoded as ASCII-8BIT. This is useful in the case where an application
-      # must handle data but encoding of the data is unknown, like file system data.
+      # encoded as ASCII-8BIT. This is useful in the case where an application must
+      # handle data but encoding of the data is unknown, like file system data.
       def skip_parameter_encoding(action)
         @_parameter_encodings[action.to_s] = Hash.new { Encoding::ASCII_8BIT }
       end
 
-      # Specify the encoding for a parameter on an action.
-      # If not specified the default is UTF-8.
+      # Specify the encoding for a parameter on an action. If not specified the
+      # default is UTF-8.
       #
       # You can specify a binary (ASCII_8BIT) parameter with:
       #
-      #   class RepositoryController < ActionController::Base
-      #     # This specifies that file_path is not UTF-8 and is instead ASCII_8BIT
-      #     param_encoding :show, :file_path, Encoding::ASCII_8BIT
+      #     class RepositoryController < ActionController::Base
+      #       # This specifies that file_path is not UTF-8 and is instead ASCII_8BIT
+      #       param_encoding :show, :file_path, Encoding::ASCII_8BIT
       #
-      #     def show
-      #       @repo = Repository.find_by_filesystem_path params[:file_path]
+      #       def show
+      #         @repo = Repository.find_by_filesystem_path params[:file_path]
       #
-      #       # params[:repo_name] remains UTF-8 encoded
-      #       @repo_name = params[:repo_name]
-      #     end
+      #         # params[:repo_name] remains UTF-8 encoded
+      #         @repo_name = params[:repo_name]
+      #       end
       #
-      #     def index
-      #       @repositories = Repository.all
+      #       def index
+      #         @repositories = Repository.all
+      #       end
       #     end
-      #   end
       #
-      # The file_path parameter on the show action would be encoded as ASCII-8BIT,
-      # but all other arguments will remain UTF-8 encoded.
-      # This is useful in the case where an application must handle data
-      # but encoding of the data is unknown, like file system data.
+      # The file_path parameter on the show action would be encoded as ASCII-8BIT, but
+      # all other arguments will remain UTF-8 encoded. This is useful in the case
+      # where an application must handle data but encoding of the data is unknown,
+      # like file system data.
       def param_encoding(action, param, encoding)
         @_parameter_encodings[action.to_s][param.to_s] = encoding
       end