Autolink FormHelper#form_with [ci-skip]

Author: jonathanhefner

actionview/lib/action_view/helpers/form_helper.rb

@@ -31,7 +31,7 @@ module Helpers # :nodoc:
     # of the resource should show the current values of those attributes.
     #
     # In \Rails, this is usually achieved by creating the form using either
-    # +form_with+ or +form_for+ and a number of related helper methods. These
+    # #form_with or +form_for+ and a number of related helper methods. These
     # methods generate an appropriate <tt>form</tt> tag and yield a form
     # builder object that knows the model the form is about. Input fields are
     # created by calling methods defined on the form builder, which means they
@@ -42,7 +42,7 @@ module Helpers # :nodoc:
     #
     # For example, to create a new person you typically set up a new instance of
     # +Person+ in the <tt>PeopleController#new</tt> action, <tt>@person</tt>, and
-    # in the view template pass that object to +form_with+ or +form_for+:
+    # in the view template pass that object to #form_with or +form_for+:
     #
     #   <%= form_with model: @person do |f| %>
     #     <%= f.label :first_name %>:
@@ -784,12 +784,12 @@ def form_with(model: false, scope: nil, url: nil, format: nil, **options, &block
         end
       end
 
-      # Creates a scope around a specific model object like +form_with+, but
+      # Creates a scope around a specific model object like #form_with, but
       # doesn't create the form tags themselves. This makes +fields_for+
       # suitable for specifying additional model objects in the same form.
       #
-      # Although the usage and purpose of +fields_for+ is similar to +form_with+'s,
-      # its method signature is slightly different. Like +form_with+, it yields
+      # Although the usage and purpose of +fields_for+ is similar to #form_with's,
+      # its method signature is slightly different. Like #form_with, it yields
       # a FormBuilder object associated with a particular model object to a block,
       # and within the block allows methods to be called on the builder to
       # generate fields associated with the model object. Fields may reflect
@@ -1033,7 +1033,7 @@ def fields_for(record_name, record_object = nil, options = {}, &block)
       end
 
       # Scopes input fields with either an explicit scope or model.
-      # Like +form_with+ does with <tt>:scope</tt> or <tt>:model</tt>,
+      # Like #form_with does with <tt>:scope</tt> or <tt>:model</tt>,
       # except it doesn't output the form tags.
       #
       #   # Using a scope prefixes the input field names:
@@ -1057,13 +1057,13 @@ def fields_for(record_name, record_object = nil, options = {}, &block)
       #     <% end %>
       #   <% end %>
       #
-      # Much like +form_with+ a FormBuilder instance associated with the scope
+      # Much like #form_with a FormBuilder instance associated with the scope
       # or model is yielded, so any generated field names are prefixed with
       # either the passed scope or the scope inferred from the <tt>:model</tt>.
       #
       # === Mixing with other form helpers
       #
-      # While +form_with+ uses a FormBuilder object it's possible to mix and
+      # While #form_with uses a FormBuilder object it's possible to mix and
       # match the stand-alone FormHelper methods and methods
       # from FormTagHelper:
       #
@@ -1221,7 +1221,7 @@ def hidden_field(object_name, method, options = {})
       # hash with +options+. These options will be tagged onto the HTML as an HTML element attribute as in the example
       # shown.
       #
-      # Using this method inside a +form_with+ block will set the enclosing form's encoding to <tt>multipart/form-data</tt>.
+      # Using this method inside a #form_with block will set the enclosing form's encoding to <tt>multipart/form-data</tt>.
       #
       # ==== Options
       # * Creates standard HTML attributes for the tag.