Reviewed form type options includes

Author: wouterj

reference/forms/types/options/action.rst.inc

@@ -6,7 +6,7 @@ action
 
 **type**: ``string`` **default**: empty string
 
-This option specifies where to send the form's data on submission (usually a
-URI). Its value is rendered as the ``action`` attribute of the ``form``
-element. An empty value is considered a same-document reference, i.e. the form
-will be submitted to the same URI that rendered the form.
+This option specifies where to send the form's data on submission (usually
+a URI). Its value is rendered as the ``action`` attribute of the ``form``
+element. An empty value is considered a same-document reference, i.e. the
+form will be submitted to the same URI that rendered the form.

reference/forms/types/options/auto_initialize.rst.inc

@@ -4,5 +4,6 @@ auto_initialize
 **type**: ``boolean``  **default**: ``true``
 
 An internal option: sets whether the form should be initialized automatically.
-For all fields, this option should only be ``true`` for root forms. You won't
-need to change this option and probably won't need to worry about it.
+For all fields, this option should only be ``true`` for root forms. You
+won't need to change this option and probably won't need to worry about
+it.

reference/forms/types/options/block_name.rst.inc

@@ -1,5 +1,5 @@
 block_name
-~~~~~~~~~~~
+~~~~~~~~~~
 
 **type**: ``string`` **default**: the form's name (see :ref:`Knowing which
 block to customize <cookbook-form-customization-sidebar>`)

reference/forms/types/options/button_label.rst.inc

@@ -3,8 +3,8 @@ label
 
 **type**: ``string`` **default**: The label is "guessed" from the field name
 
-Sets the label that will be displayed on the button. The label can also be
-directly set inside the template:
+Sets the label that will be displayed on the button. The label can also
+be directly set inside the template:
 
 .. configuration-block::
 

reference/forms/types/options/by_reference.rst.inc

@@ -40,6 +40,7 @@ So, all that ``by_reference=false`` really does is force the framework to
 call the setter on the parent object.
 
 Similarly, if you're using the :doc:`collection</reference/forms/types/collection>`
-form type where your underlying collection data is an object (like with Doctrine's
-``ArrayCollection``), then ``by_reference`` must be set to ``false`` if you
-need the adder and remover (e.g. ``addAuthor()`` and ``removeAuthor()``) to be called.
+form type where your underlying collection data is an object (like with
+Doctrine's ``ArrayCollection``), then ``by_reference`` must be set to ``false``
+if you need the adder and remover (e.g. ``addAuthor()`` and ``removeAuthor()``)
+to be called.

reference/forms/types/options/cascade_validation.rst.inc

@@ -11,9 +11,10 @@ the data from ``CategoryType`` to also be validated.
 .. tip::
 
     Instead of using this option, it is recommended that you use the ``Valid``
-    constraint in your model to force validation on a child object stored on
-    a property. This cascades only the validation but not the use of the
-    ``validation_group`` option on child forms. You can read more about this
-    in the section about :ref:`Embedding a Single Object <forms-embedding-single-object>`.
+    constraint in your model to force validation on a child object stored
+    on a property. This cascades only the validation but not the use of
+    the ``validation_group`` option on child forms. You can read more
+    about this in the section about
+    :ref:`Embedding a Single Object <forms-embedding-single-object>`.
 
 .. include:: /reference/forms/types/options/_error_bubbling_hint.rst.inc

reference/forms/types/options/compound.rst.inc

@@ -3,6 +3,6 @@ compound
 
 **type**: ``boolean`` **default**: ``true``
 
-This option specifies if a form is compound. This is independent of whether the
-form actually has children. A form can be compound but not have any children
-at all (e.g. an empty collection form).
+This option specifies if a form is compound. This is independent of whether
+the form actually has children. A form can be compound but not have any
+children at all (e.g. an empty collection form).

reference/forms/types/options/data.rst.inc

@@ -5,15 +5,15 @@ data
 
 When you create a form, each field initially displays the value of the
 corresponding property of the form's domain object (if an object is bound
-to the form). If you want to override the initial value for the form or just
-an individual field, you can set it in the data option::
+to the form). If you want to override the initial value for the form or
+just an individual field, you can set it in the data option::
 
     $builder->add('token', 'hidden', array(
         'data' => 'abcdef',
     ));
 
 .. note::
 
-    The default values for form fields are taken directly from the
-    underlying data structure (e.g. an entity or an array).
-    The ``data`` option overrides this default value.
+    The default values for form fields are taken directly from the underlying
+    data structure (e.g. an entity or an array). The ``data`` option overrides
+    this default value.

reference/forms/types/options/data_class.rst.inc

@@ -3,8 +3,8 @@ data_class
 
 **type**: ``string``
 
-This option is used to set the appropriate data mapper to be used by the form,
-so you can use it for any form field type which requires an object.
+This option is used to set the appropriate data mapper to be used by the
+form, so you can use it for any form field type which requires an object.
 
 .. code-block:: php
 

reference/forms/types/options/date_format.rst.inc

@@ -4,12 +4,12 @@ format
 **type**: ``integer`` or ``string`` **default**: `IntlDateFormatter::MEDIUM`_
 (or ``yyyy-MM-dd`` if `widget`_ is ``single_text``)
 
-Option passed to the ``IntlDateFormatter`` class, used to transform user input
-into the proper format. This is critical when the `widget`_ option is
-set to ``single_text``, and will define how the user will input the data.
+Option passed to the ``IntlDateFormatter`` class, used to transform user
+input into the proper format. This is critical when the `widget`_ option
+is set to ``single_text`` and will define how the user will input the data.
 By default, the format is determined based on the current user locale: meaning
-that *the expected format will be different for different users*. You
-can override it by passing the format as a string.
+that *the expected format will be different for different users*. You can
+override it by passing the format as a string.
 
 For more information on valid formats, see `Date/Time Format Syntax`_::
 
@@ -21,9 +21,10 @@ For more information on valid formats, see `Date/Time Format Syntax`_::
 
 .. note::
 
-    If you want your field to be rendered as an HTML5 "date" field, you have to
-    use a ``single_text`` widget with the ``yyyy-MM-dd`` format (the `RFC 3339`_
-    format) which is the default value if you use the ``single_text`` widget.
+    If you want your field to be rendered as an HTML5 "date" field, you
+    have to use a ``single_text`` widget with the ``yyyy-MM-dd`` format
+    (the `RFC 3339`_ format) which is the default value if you use the
+    ``single_text`` widget.
 
 .. _`Date/Time Format Syntax`: http://userguide.icu-project.org/formatparse/datetime#TOC-Date-Time-Format-Syntax
 .. _`IntlDateFormatter::MEDIUM`: http://www.php.net/manual/en/class.intldateformatter.php#intl.intldateformatter-constants