symfony
diff --git a/‎form/create_custom_field_type.rst
Lines changed: 4 additions & 0 deletions b/‎form/create_custom_field_type.rst
Lines changed: 4 additions & 0 deletions
diff --git a/‎form/create_form_type_extension.rst
Lines changed: 4 additions & 0 deletions b/‎form/create_form_type_extension.rst
Lines changed: 4 additions & 0 deletions
diff --git a/‎form/data_transformers.rst
Lines changed: 5 additions & 0 deletions b/‎form/data_transformers.rst
Lines changed: 5 additions & 0 deletions
diff --git a/‎form/dynamic_form_modification.rst
Lines changed: 4 additions & 0 deletions b/‎form/dynamic_form_modification.rst
Lines changed: 4 additions & 0 deletions
diff --git a/‎form/form_dependencies.rst
Lines changed: 4 additions & 0 deletions b/‎form/form_dependencies.rst
Lines changed: 4 additions & 0 deletions
diff --git a/‎form/type_guesser.rst
Lines changed: 4 additions & 0 deletions b/‎form/type_guesser.rst
Lines changed: 4 additions & 0 deletions
@@ -339,6 +339,10 @@ the ``genders`` parameter value as the first argument to its to-be-created
     Make sure the services file is being imported. See :ref:`service-container-imports-directive`
     for details.
 
+.. versionadded:: 3.3
+    Prior to Symfony 3.3, you needed to define form type services as ``public``.
+    Starting from Symfony 3.3, you can also define them as ``private``.
+
 First, add a ``__construct`` method to ``GenderType``, which receives the gender
 configuration::
 
 
@@ -131,6 +131,10 @@ The ``extended_type`` key of the tag is the type of field that this extension sh
 be applied to. In your case, as you want to extend the ``Symfony\Component\Form\Extension\Core\Type\FileType``
 field type, you will use that as the ``extended_type``.
 
+.. versionadded:: 3.3
+    Prior to Symfony 3.3, you needed to define type extension services as ``public``.
+    Starting from Symfony 3.3, you can also define them as ``private``.
+
 .. tip::
 
     There is an optional tag attribute called ``priority``, which 
 
@@ -334,11 +334,16 @@ Define the form type as a service in your configuration files.
             )
             ->addTag('form.type')
         ;
+
 .. tip::
 
     For more information about defining form types as services, read
     :doc:`register your form type as a service </form/form_dependencies>`.
 
+.. versionadded:: 3.3
+    Prior to Symfony 3.3, you needed to define form type services as ``public``.
+    Starting from Symfony 3.3, you can also define them as ``private``.
+
 Now, you can easily use your ``TaskType``::
 
     // e.g. in a controller somewhere
 
@@ -370,6 +370,10 @@ you need to register it as a service and tag it with :ref:`form.type <dic-tags-f
 
         $container->setDefinition('app.form.friend_message', $definition);
 
+.. versionadded:: 3.3
+    Prior to Symfony 3.3, you needed to define form type services as ``public``.
+    Starting from Symfony 3.3, you can also define them as ``private``.
+
 In a controller that extends the :class:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller`
 class, you can simply call::
 
 
@@ -136,6 +136,10 @@ Next, register this as a service and tag it with ``form.type``:
             ->addTag('form.type')
         ;
 
+.. versionadded:: 3.3
+    Prior to Symfony 3.3, you needed to define form type services as ``public``.
+    Starting from Symfony 3.3, you can also define them as ``private``.
+
 That's it! Your controller - where you create the form - doesn't need to change
 at all: Symfony is smart enough to load the ``TaskType`` from the container.
 
 
@@ -217,6 +217,10 @@ creating a service and tagging it as ``form.type_guesser``:
             ->addTag('form.type_guesser')
         ;
 
+.. versionadded:: 3.3
+    Prior to Symfony 3.3, you needed to define type guesser services as ``public``.
+    Starting from Symfony 3.3, you can also define them as ``private``.
+
 .. sidebar:: Registering a Type Guesser in the Component
 
     If you're using the Form component standalone in your PHP project, use
Original file line number	Diff line number	Diff line change
`@@ -334,11 +334,16 @@ Define the form type as a service in your configuration files.`
`334`	`334`	`)`
`335`	`335`	`->addTag('form.type')`
`336`	`336`	`;`
	`337`	`+`
`337`	`338`	`.. tip::`
`338`	`339`
`339`	`340`	`For more information about defining form types as services, read`
`340`	`341`	:doc:`register your form type as a service </form/form_dependencies>`.
`341`	`342`
	`343`	`+.. versionadded:: 3.3`
	`344`	+ Prior to Symfony 3.3, you needed to define form type services as ``public``.
	`345`	+ Starting from Symfony 3.3, you can also define them as ``private``.
	`346`	`+`
`342`	`347`	Now, you can easily use your ``TaskType``::
`343`	`348`
`344`	`349`	`// e.g. in a controller somewhere`
Original file line number	Diff line number	Diff line change
@@ -136,6 +136,10 @@ Next, register this as a service and tag it with ``form.type``:
`136`	`136`	`->addTag('form.type')`
`137`	`137`	`;`
`138`	`138`
	`139`	`+.. versionadded:: 3.3`
	`140`	+ Prior to Symfony 3.3, you needed to define form type services as ``public``.
	`141`	+ Starting from Symfony 3.3, you can also define them as ``private``.
	`142`	`+`
`139`	`143`	`That's it! Your controller - where you create the form - doesn't need to change`
`140`	`144`	at all: Symfony is smart enough to load the ``TaskType`` from the container.
`141`	`145`
Original file line number	Diff line number	Diff line change
@@ -217,6 +217,10 @@ creating a service and tagging it as ``form.type_guesser``:
`217`	`217`	`->addTag('form.type_guesser')`
`218`	`218`	`;`
`219`	`219`
	`220`	`+.. versionadded:: 3.3`
	`221`	+ Prior to Symfony 3.3, you needed to define type guesser services as ``public``.
	`222`	+ Starting from Symfony 3.3, you can also define them as ``private``.
	`223`	`+`
`220`	`224`	`.. sidebar:: Registering a Type Guesser in the Component`
`221`	`225`
`222`	`226`	`If you're using the Form component standalone in your PHP project, use`