use boolean instead of Boolean

Author: Christian Flothmann

book/forms.rst

@@ -198,7 +198,7 @@ it into a format that's suitable for being rendered in an HTML form.
    ``task`` property via the ``getTask()`` and ``setTask()`` methods on the
    ``Task`` class. Unless a property is public, it *must* have a "getter" and
    "setter" method so that the Form component can get and put data onto the
-   property. For a Boolean property, you can use an "isser" or "hasser" method
+   property. For a boolean property, you can use an "isser" or "hasser" method
    (e.g. ``isPublished()`` or ``hasReminder()``) instead of a getter (e.g.
    ``getPublished()`` or ``getReminder()``).
 

components/yaml/yaml_format.rst

@@ -119,7 +119,7 @@ Nulls in YAML can be expressed with ``null`` or ``~``.
 Booleans
 ~~~~~~~~
 
-Booleans in YAML are expressed with ``true`` and ``false``.
+booleans in YAML are expressed with ``true`` and ``false``.
 
 Dates
 ~~~~~

contributing/code/standards.rst

@@ -79,7 +79,7 @@ example containing most features described below:
 
             throw new \RuntimeException(sprintf('Unrecognized dummy option "%s"', $dummy));
         }
-        
+
         private function reverseBoolean($value = null, $theSwitch = false)
         {
             if (!$theSwitch) {
@@ -95,7 +95,7 @@ Structure
 
 * Add a single space after each comma delimiter;
 
-* Add a single space around binary operators (``==``, ``&&``, ...), with 
+* Add a single space around binary operators (``==``, ``&&``, ...), with
   the exception of the concatenation (``.``) operator;
 
 * Place unary operators (``!``, ``--``, ...) adjacent to the affected variable;

cookbook/configuration/using_parameters_in_dic.rst

@@ -105,7 +105,7 @@ be injected with this parameter via the extension as follows::
 
         public function  __construct($debug)
         {
-            $this->debug = (Boolean) $debug;
+            $this->debug = (bool) $debug;
         }
 
         public function getConfigTreeBuilder()

cookbook/doctrine/registration_form.rst

@@ -194,7 +194,7 @@ Start by creating a simple class which represents the "registration"::
 
         public function setTermsAccepted($termsAccepted)
         {
-            $this->termsAccepted = (Boolean) $termsAccepted;
+            $this->termsAccepted = (bool) $termsAccepted;
         }
     }
 

cookbook/security/voters_data_permission.rst

@@ -121,7 +121,7 @@ edit a particular object. Here's an example implementation::
             switch($attribute) {
                 case self::VIEW:
                     // the data object could have for example a method isPrivate()
-                    // which checks the Boolean attribute $private
+                    // which checks the boolean attribute $private
                     if (!$post->isPrivate()) {
                         return VoterInterface::ACCESS_GRANTED;
                     }

reference/configuration/framework.rst

@@ -67,7 +67,7 @@ http_method_override
 .. versionadded:: 2.3
     The ``http_method_override`` option was introduced in Symfony 2.3.
 
-**type**: ``Boolean`` **default**: ``true``
+**type**: ``boolean`` **default**: ``true``
 
 This determines whether the ``_method`` request parameter is used as the intended
 HTTP method on POST requests. If enabled, the
@@ -138,7 +138,7 @@ is set, then the ``ide`` option will be ignored.
 test
 ~~~~
 
-**type**: ``Boolean``
+**type**: ``boolean``
 
 If this configuration parameter is present (and not ``false``), then the
 services related to testing your application (e.g. ``test.client``) are loaded.
@@ -235,14 +235,14 @@ to the cookie specification.
 cookie_secure
 .............
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 This determines whether cookies should only be sent over secure connections.
 
 cookie_httponly
 ...............
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 This determines whether cookies should only be accessible through the HTTP protocol.
 This means that the cookie won't be accessible by scripting languages, such

reference/configuration/security.rst

@@ -265,7 +265,7 @@ The Login Form and Process
     Be sure that this URL is covered by your main firewall (i.e. don't create
     a separate firewall just for ``check_path`` URL).
 
-*   ``use_forward`` (type: ``Boolean``, default: ``false``)
+*   ``use_forward`` (type: ``boolean``, default: ``false``)
     If you'd like the user to be forwarded to the login form instead of
     being redirected, set this option to ``true``.
 
@@ -279,18 +279,18 @@ The Login Form and Process
     your login form. When you submit the form to ``check_path``, the security
     system will look for a POST parameter with this name.
 
-*   ``post_only`` (type: ``Boolean``, default: ``true``)
+*   ``post_only`` (type: ``boolean``, default: ``true``)
     By default, you must submit your login form to the ``check_path`` URL
     as a POST request. By setting this option to ``false``, you can send a
     GET request to the ``check_path`` URL.
 
 Redirecting after Login
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-* ``always_use_default_target_path`` (type: ``Boolean``, default: ``false``)
+* ``always_use_default_target_path`` (type: ``boolean``, default: ``false``)
 * ``default_target_path`` (type: ``string``, default: ``/``)
 * ``target_path_parameter`` (type: ``string``, default: ``_target_path``)
-* ``use_referer`` (type: ``Boolean``, default: ``false``)
+* ``use_referer`` (type: ``boolean``, default: ``false``)
 
 .. _reference-security-pbkdf2:
 

reference/configuration/swiftmailer.rst

@@ -159,15 +159,15 @@ on the ``X-Swift-To``, ``X-Swift-Cc`` and ``X-Swift-Bcc`` headers.
 disable_delivery
 ~~~~~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If true, the ``transport`` will automatically be set to ``null``, and no
 emails will actually be delivered.
 
 logging
 ~~~~~~~
 
-**type**: ``Boolean`` **default**: ``%kernel.debug%``
+**type**: ``boolean`` **default**: ``%kernel.debug%``
 
 If true, Symfony's data collector will be activated for Swift Mailer and the
 information will be available in the profiler.

reference/constraints/Choice.rst

@@ -89,11 +89,11 @@ If your valid choice list is simple, you can pass them in directly via the
 
         use Symfony\Component\Validator\Mapping\ClassMetadata;
         use Symfony\Component\Validator\Constraints as Assert;
-        
+
         class Author
         {
             protected $gender;
-            
+
             public static function loadValidatorMetadata(ClassMetadata $metadata)
             {
                 $metadata->addPropertyConstraint('gender', new Assert\Choice(array(
@@ -176,11 +176,11 @@ constraint.
 
         use Symfony\Component\Validator\Mapping\ClassMetadata;
         use Symfony\Component\Validator\Constraints as Assert;
-        
+
         class Author
         {
             protected $gender;
-            
+
             public static function loadValidatorMetadata(ClassMetadata $metadata)
             {
                 $metadata->addPropertyConstraint('gender', new Assert\Choice(array(
@@ -244,11 +244,11 @@ you can pass the class name and the method as an array.
 
         use Symfony\Component\Validator\Mapping\ClassMetadata;
         use Symfony\Component\Validator\Constraints as Assert;
-        
+
         class Author
         {
             protected $gender;
-            
+
             public static function loadValidatorMetadata(ClassMetadata $metadata)
             {
                 $metadata->addPropertyConstraint('gender', new Assert\Choice(array(
@@ -281,7 +281,7 @@ for details on its usage.
 multiple
 ~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If this option is true, the input value is expected to be an array instead
 of a single, scalar value. The constraint will check that each value of
@@ -344,7 +344,7 @@ too many options per the `max`_ option.
 strict
 ~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If true, the validator will also check the type of the input value. Specifically,
 this value is passed to as the third argument to the PHP :phpfunction:`in_array` method

reference/constraints/Collection.rst

@@ -298,7 +298,7 @@ be executed against that element of the collection.
 allowExtraFields
 ~~~~~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: false
+**type**: ``boolean`` **default**: false
 
 If this option is set to ``false`` and the underlying collection contains
 one or more elements that are not included in the `fields`_ option, a validation
@@ -307,14 +307,14 @@ error will be returned. If set to ``true``, extra fields are ok.
 extraFieldsMessage
 ~~~~~~~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``The fields {{ fields }} were not expected.``
+**type**: ``boolean`` **default**: ``The fields {{ fields }} were not expected.``
 
 The message shown if `allowExtraFields`_ is false and an extra field is detected.
 
 allowMissingFields
 ~~~~~~~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: false
+**type**: ``boolean`` **default**: false
 
 If this option is set to ``false`` and one or more fields from the `fields`_
 option are not present in the underlying collection, a validation error will
@@ -324,7 +324,7 @@ option are not present in the underlying collection.
 missingFieldsMessage
 ~~~~~~~~~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``The fields {{ fields }} are missing.``
+**type**: ``boolean`` **default**: ``The fields {{ fields }} are missing.``
 
 The message shown if `allowMissingFields`_ is false and one or more fields
 are missing from the underlying collection.

reference/constraints/Email.rst

@@ -99,15 +99,15 @@ This message is shown if the underlying data is not a valid email address.
 checkMX
 ~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If true, then the :phpfunction:`checkdnsrr` PHP function will be used to
 check the validity of the MX record of the host of the given email.
 
 checkHost
 ~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If true, then the :phpfunction:`checkdnsrr` PHP function will be used to
 check the validity of the MX *or* the A *or* the AAAA record of the host

reference/constraints/False.rst

@@ -104,7 +104,7 @@ method returns **false**:
 .. caution::
 
     When using YAML, be sure to surround ``False`` with quotes (``'False'``)
-    or else YAML will convert this into a ``false`` Boolean value.
+    or else YAML will convert this into a ``false`` boolean value.
 
 Options
 -------

reference/constraints/Isbn.rst

@@ -106,15 +106,15 @@ Available Options
 isbn10
 ~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If this required option is set to ``true`` the constraint will check if the
 code is a valid ISBN-10 code.
 
 isbn13
 ~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If this required option is set to ``true`` the constraint will check if the
 code is a valid ISBN-13 code.

reference/constraints/Issn.rst

@@ -90,15 +90,15 @@ The message shown if the given value is not a valid ISSN.
 caseSensitive
 ~~~~~~~~~~~~~
 
-**type**: ``Boolean`` default: ``false``
+**type**: ``boolean`` default: ``false``
 
 The validator will allow ISSN values to end with a lower case 'x' by default.
 When switching this to ``true``, the validator requires an upper case 'X'.
 
 requireHyphen
 ~~~~~~~~~~~~~
 
-**type**: ``Boolean`` default: ``false``
+**type**: ``boolean`` default: ``false``
 
 The validator will allow non hyphenated ISSN values by default. When switching
 this to ``true``, the validator requires a hyphenated ISSN value.

reference/constraints/Regex.rst

@@ -180,7 +180,7 @@ htmlPattern
 .. versionadded:: 2.1
     The ``htmlPattern`` option was introduced in Symfony 2.1
 
-**type**: ``string|Boolean`` **default**: null
+**type**: ``string|boolean`` **default**: null
 
 This option specifies the pattern to use in the HTML5 ``pattern`` attribute.
 You usually don't need to specify this option because by default, the constraint
@@ -264,7 +264,7 @@ Setting ``htmlPattern`` to false will disable client side validation.
 match
 ~~~~~
 
-**type**: ``Boolean`` default: ``true``
+**type**: ``boolean`` default: ``true``
 
 If ``true`` (or not set), this validator will pass if the given string matches
 the given `pattern`_ regular expression. However, when this option is set

reference/constraints/True.rst

@@ -120,7 +120,7 @@ If the ``isTokenValid()`` returns false, the validation will fail.
 .. caution::
 
     When using YAML, be sure to surround ``True`` with quotes (``'True'``)
-    or else YAML will convert this into a ``true`` Boolean value.
+    or else YAML will convert this into a ``true`` boolean value.
 
 Options
 -------

reference/constraints/UniqueEntity.rst

@@ -257,7 +257,7 @@ Now, the message would be bound to the ``port`` field with this configuration.
 ignoreNull
 ~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``true``
+**type**: ``boolean`` **default**: ``true``
 
 .. versionadded:: 2.1
     The ``ignoreNull`` option was introduced in Symfony 2.1.

reference/forms/types/checkbox.rst

@@ -5,7 +5,7 @@ checkbox Field Type
 ===================
 
 Creates a single input checkbox. This should always be used for a field that
-has a Boolean value: if the box is checked, the field will be set to true,
+has a boolean value: if the box is checked, the field will be set to true,
 if the box is unchecked, the value will be set to false.
 
 +-------------+------------------------------------------------------------------------+

reference/forms/types/choice.rst

@@ -192,9 +192,9 @@ Field Variables
 +------------------------+--------------+-------------------------------------------------------------------+
 | Variable               | Type         | Usage                                                             |
 +========================+==============+===================================================================+
-| multiple               | ``Boolean``  | The value of the `multiple`_ option.                              |
+| multiple               | ``boolean``  | The value of the `multiple`_ option.                              |
 +------------------------+--------------+-------------------------------------------------------------------+
-| expanded               | ``Boolean``  | The value of the `expanded`_ option.                              |
+| expanded               | ``boolean``  | The value of the `expanded`_ option.                              |
 +------------------------+--------------+-------------------------------------------------------------------+
 | preferred_choices      | ``array``    | A nested array containing the ``ChoiceView`` objects of           |
 |                        |              | choices which should be presented to the user with priority.      |
@@ -210,7 +210,7 @@ Field Variables
 | is_selected            | ``callable`` | A callable which takes a ``ChoiceView`` and the selected value(s) |
 |                        |              | and returns whether the choice is in the selected value(s).       |
 +------------------------+--------------+-------------------------------------------------------------------+
-| empty_value_in_choices | ``Boolean``  | Whether the empty value is in the choice list.                    |
+| empty_value_in_choices | ``boolean``  | Whether the empty value is in the choice list.                    |
 +------------------------+--------------+-------------------------------------------------------------------+
 
 .. tip::