Fix Missing Wording

gary houbre · gary houbre · commit c4f9bf10a938 · 2020-10-06T09:11:40.000+02:00
diff --git a/deployment/fortrabbit.rst b/deployment/fortrabbit.rst
@@ -9,4 +9,4 @@ Deploying to fortrabbit
 For details on deploying to fortrabbit, see their official documentation:
 `Install Symfony`_
 
-.. _`Install Symfony`: https://help.fortrabbit.com/install-symfony-3-uni
+.. _`Install Symfony`: https://help.fortrabbit.com/install-symfony-5-uni
diff --git a/doctrine/associations.rst b/doctrine/associations.rst
@@ -548,6 +548,7 @@ What about *removing* a ``Product`` from a ``Category``? The ``make:entity`` com
 also generated a ``removeProduct()`` method::
 
     // src/Entity/Category.php
+    namespace App\Entity;
 
     // ...
     class Category
diff --git a/doctrine/events.rst b/doctrine/events.rst
@@ -56,6 +56,8 @@ define a callback for the ``prePersist`` Doctrine event:
     .. code-block:: php-annotations
 
         // src/Entity/Product.php
+        namespace App\Entity;
+
         use Doctrine\ORM\Mapping as ORM;
 
         // When using annotations, don't forget to add @ORM\HasLifecycleCallbacks()
diff --git a/doctrine/multiple_entity_managers.rst b/doctrine/multiple_entity_managers.rst
@@ -236,6 +236,9 @@ When working with multiple entity managers to generate migrations:
 If you *do* omit the entity manager's name when asking for it,
 the default entity manager (i.e. ``default``) is returned::
 
+    // src/Controller/UserController.php
+    namespace App\Controller;
+
     // ...
 
     use Doctrine\ORM\EntityManagerInterface;
@@ -262,6 +265,9 @@ entity manager to persist and fetch its entities.
 
 The same applies to repository calls::
 
+    // src/Controller/UserController.php
+    namespace App\Controller;
+
     use AcmeStoreBundle\Entity\Customer;
     use AcmeStoreBundle\Entity\Product;
     // ...
diff --git a/doctrine/resolve_target_entity.rst b/doctrine/resolve_target_entity.rst
@@ -42,8 +42,8 @@ A Customer entity::
     // src/Entity/Customer.php
     namespace App\Entity;
 
-    use Acme\CustomerBundle\Entity\Customer as BaseCustomer;
-    use Acme\InvoiceBundle\Model\InvoiceSubjectInterface;
+    use App\Entity\CustomerInterface as BaseCustomer;
+    use App\Model\InvoiceSubjectInterface;
     use Doctrine\ORM\Mapping as ORM;
 
     /**
@@ -58,10 +58,10 @@ A Customer entity::
 
 An Invoice entity::
 
-    // src/Acme/InvoiceBundle/Entity/Invoice.php
-    namespace Acme\InvoiceBundle\Entity;
+    // src/Entity/Invoice.php
+    namespace App\Entity;
 
-    use Acme\InvoiceBundle\Model\InvoiceSubjectInterface;
+    use App\Model\InvoiceSubjectInterface;
     use Doctrine\ORM\Mapping as ORM;
 
     /**
@@ -73,16 +73,16 @@ An Invoice entity::
     class Invoice
     {
         /**
-         * @ORM\ManyToOne(targetEntity="Acme\InvoiceBundle\Model\InvoiceSubjectInterface")
+         * @ORM\ManyToOne(targetEntity="App\Model\InvoiceSubjectInterface")
          * @var InvoiceSubjectInterface
          */
         protected $subject;
     }
 
 An InvoiceSubjectInterface::
 
-    // src/Acme/InvoiceBundle/Model/InvoiceSubjectInterface.php
-    namespace Acme\InvoiceBundle\Model;
+    // src/Model/InvoiceSubjectInterface.php
+    namespace App\Model;
 
     /**
      * An interface that the invoice Subject object should implement.
@@ -115,7 +115,7 @@ about the replacement:
             orm:
                 # ...
                 resolve_target_entities:
-                    Acme\InvoiceBundle\Model\InvoiceSubjectInterface: App\Entity\Customer
+                    App\Model\InvoiceSubjectInterface: App\Entity\Customer
 
     .. code-block:: xml
 
@@ -132,15 +132,15 @@ about the replacement:
             <doctrine:config>
                 <doctrine:orm>
                     <!-- ... -->
-                    <doctrine:resolve-target-entity interface="Acme\InvoiceBundle\Model\InvoiceSubjectInterface">App\Entity\Customer</doctrine:resolve-target-entity>
+                    <doctrine:resolve-target-entity interface="App\Model\InvoiceSubjectInterface">App\Entity\Customer</doctrine:resolve-target-entity>
                 </doctrine:orm>
             </doctrine:config>
         </container>
 
     .. code-block:: php
 
         // config/packages/doctrine.php
-        use Acme\InvoiceBundle\Model\InvoiceSubjectInterface;
+        use App\Model\InvoiceSubjectInterface;
         use App\Entity\Customer;
 
         $container->loadFromExtension('doctrine', [
diff --git a/form/create_custom_field_type.rst b/form/create_custom_field_type.rst
@@ -287,6 +287,8 @@ to define, validate and process their values::
 Now you can configure these options when using the form type::
 
     // src/Form/Type/OrderType.php
+    namespace App\Form\Type;
+
     // ...
 
     class OrderType extends AbstractType
@@ -310,6 +312,8 @@ Now you can configure these options when using the form type::
 The last step is to use these options when building the form::
 
     // src/Form/Type/PostalAddressType.php
+    namespace App\Form\Type;
+
     // ...
 
     class PostalAddressType extends AbstractType
@@ -447,6 +451,8 @@ defined by the form or be completely independent::
 
 
     // src/Form/Type/PostalAddressType.php
+    namespace App\Form\Type;
+
     use Doctrine\ORM\EntityManagerInterface;
     // ...
 
diff --git a/form/create_form_type_extension.rst b/form/create_form_type_extension.rst
@@ -251,6 +251,8 @@ may not be applied to it.
 Another option is to return multiple form types in the ``getExtendedTypes()``
 method to extend all of them::
 
+    // src/Form/Extension/DateTimeExtension.php
+    namespace App\Form\Extension;
     // ...
     use Symfony\Component\Form\Extension\Core\Type\DateTimeType;
     use Symfony\Component\Form\Extension\Core\Type\DateType;
diff --git a/form/dynamic_form_modification.rst b/form/dynamic_form_modification.rst
@@ -255,6 +255,8 @@ Now that you have all the basics in place you can use the features of the
 security helper to fill in the listener logic::
 
     // src/Form/Type/FriendMessageFormType.php
+    namespace App\Form\Type;
+
     use App\Entity\User;
     use Doctrine\ORM\EntityRepository;
     use Symfony\Bridge\Doctrine\Form\Type\EntityType;
diff --git a/form/inherit_data_option.rst b/form/inherit_data_option.rst
@@ -126,6 +126,8 @@ access the properties of the ``Customer`` instance instead. Convenient, eh?
 Finally, make this work by adding the location form to your two original forms::
 
     // src/Form/Type/CompanyType.php
+    namespace App\Form\Type;
+
     use App\Entity\Company;
     // ...
 
@@ -141,6 +143,8 @@ Finally, make this work by adding the location form to your two original forms::
 .. code-block:: php
 
     // src/Form/Type/CustomerType.php
+    namespace App\Form\Type;
+
     use App\Entity\Customer;
     // ...
 
diff --git a/form/use_empty_data.rst b/form/use_empty_data.rst
@@ -44,6 +44,7 @@ that takes arguments. Remember, the default ``data_class`` option calls
 that constructor with no arguments::
 
     // src/Form/Type/BlogType.php
+    namespace App\Form\Type;
 
     // ...
     use App\Entity\Blog;
diff --git a/http_cache/esi.rst b/http_cache/esi.rst
@@ -98,7 +98,8 @@ ticker at the bottom of the content. With ESI, you can cache the news ticker
 independently of the rest of the page::
 
     // src/Controller/DefaultController.php
-
+    namespace App\Controller;
+    
     // ...
     class DefaultController extends AbstractController
     {
diff --git a/http_cache/ssi.rst b/http_cache/ssi.rst
@@ -85,7 +85,8 @@ to cache a static GDPR content block. With SSI, you can add some expiration
 on this block and keep the page private::
 
     // src/Controller/ProfileController.php
-
+    namespace App\Controller;
+    
     // ...
     class ProfileController extends AbstractController
     {
diff --git a/logging/monolog_console.rst b/logging/monolog_console.rst
@@ -35,6 +35,9 @@ the current log level and the console verbosity.
 
 The example above could then be rewritten as::
 
+    // src/Command/YourCommand.php
+    namespace App\Command;
+
     use Psr\Log\LoggerInterface;
     use Symfony\Component\Console\Command\Command;
     use Symfony\Component\Console\Input\InputInterface;
diff --git a/logging/processors.rst b/logging/processors.rst
@@ -16,6 +16,7 @@ Sometimes it is hard to tell which entries in the log belong to which session
 and/or request. The following example will add a unique token for each request
 using a processor::
 
+    // src/Logger/SessionRequestProcessor.php
     namespace App\Logger;
 
     use Symfony\Component\HttpFoundation\Session\SessionInterface;
diff --git a/messenger/dispatch_after_current_bus.rst b/messenger/dispatch_after_current_bus.rst
@@ -44,6 +44,7 @@ are dispatched by a handler once that handler has fully finished. This can be by
 using the ``DispatchAfterCurrentBusMiddleware`` and adding a
 ``DispatchAfterCurrentBusStamp`` stamp to :ref:`the message Envelope <messenger-envelopes>`::
 
+    // src/Messenger/CommandHandler/RegisterUserHandler.php
     namespace App\Messenger\CommandHandler;
 
     use App\Entity\User;
@@ -85,6 +86,7 @@ using the ``DispatchAfterCurrentBusMiddleware`` and adding a
 
 .. code-block:: php
 
+    // src/Messenger/EventSubscriber/WhenUserRegisteredThenSendWelcomeEmail.php
     namespace App\Messenger\EventSubscriber;
 
     use App\Entity\User;
diff --git a/reference/configuration/kernel.rst b/reference/configuration/kernel.rst
@@ -38,6 +38,8 @@ To change this value, override the ``getCharset()`` method and return another
 charset::
 
     // src/Kernel.php
+    namespace App;
+
     use Symfony\Component\HttpKernel\Kernel as BaseKernel;
     // ...
 
@@ -71,6 +73,8 @@ override the :method:`Symfony\\Component\\HttpKernel\\Kernel::getProjectDir`
 method to return the right project directory::
 
     // src/Kernel.php
+    namespace App;
+
     use Symfony\Component\HttpKernel\Kernel as BaseKernel;
     // ...
 
diff --git a/reference/forms/types/options/choice_loader.rst.inc b/reference/forms/types/options/choice_loader.rst.inc
@@ -1,75 +1,39 @@
-choice_loader
-~~~~~~~~~~~~~
-
-**type**: :class:`Symfony\\Component\\Form\\ChoiceList\\Loader\\ChoiceLoaderInterface`
-
-The ``choice_loader`` option can be used instead of the ``choices`` option. It
+choice_loader ~~~~~~~~~~~~~ **type**:
+:class:`Symfony\\Component\\Form\\ChoiceList\\Loader\\ChoiceLoaderInterface` The
+``choice_loader`` option can be used instead of the ``choices`` option. It
 allows to create a list lazily or partially when fetching only the choices for a
 set of submitted values (i.e. querying a search engine like ``ElasticSearch``
-can be a heavy process).
-
-You can use an instance of :class:`Symfony\\Component\\Form\\ChoiceList\\Loader\\CallbackChoiceLoader`
-if you want to take advantage of lazy loading::
-
-    use App\StaticClass;
-    use Symfony\Component\Form\ChoiceList\Loader\CallbackChoiceLoader;
-    use Symfony\Component\Form\Extension\Core\Type\ChoiceType;
-    // ...
-
-    $builder->add('loaded_choices', ChoiceType::class, [
-        'choice_loader' => new CallbackChoiceLoader(function() {
-            return StaticClass::getConstants();
-        }),
-    ]);
-
+can be a heavy process). You can use an instance of
+:class:`Symfony\\Component\\Form\\ChoiceList\\Loader\\CallbackChoiceLoader` if
+you want to take advantage of lazy loading:: use App\StaticClass; use
+Symfony\Component\Form\ChoiceList\Loader\CallbackChoiceLoader; use
+Symfony\Component\Form\Extension\Core\Type\ChoiceType; // ...
+$builder->add('loaded_choices', ChoiceType::class, [ 'choice_loader' => new
+CallbackChoiceLoader(function() { return StaticClass::getConstants(); }), ]);
 This will cause the call of ``StaticClass::getConstants()`` to not happen if the
 request is redirected and if there is no pre set or submitted data. Otherwise
-the choice options would need to be resolved thus triggering the callback.
-
-When you're defining a custom choice type that may be reused in many fields
-(like entries of a collection) or reused in multiple forms at once, you
-should use the :class:`Symfony\\Component\\Form\\ChoiceList\\ChoiceList`
-static methods to wrap the loader and make the choice list cacheable for
-better performance::
-
-    use App\Form\ChoiceList\CustomChoiceLoader;
-    use App\StaticClass;
-    use Symfony\Component\Form\AbstractType;
-    use Symfony\Component\Form\ChoiceList\ChoiceList;
-    use Symfony\Component\Form\Extension\Core\Type\ChoiceType;
-    use Symfony\Component\OptionsResolver\Options;
-    use Symfony\Component\OptionsResolver\OptionsResolver;
-
-    class ConstantsType extends AbstractType
-    {
-        public static function getExtendedTypes(): iterable
-        {
-            return [ChoiceType::class];
-        }
-
-        public function configureOptions(OptionsResolver $resolver)
-        {
-            $resolver->setDefaults([
-                // the example below will create a CallbackChoiceLoader from the callable
-                'choice_loader' => ChoiceList::lazy($this, function() {
-                    return StaticClass::getConstants();
-                }),
-
-                // you can pass your own loader as well, depending on other options
-                'some_key' => null,
-                'choice_loader' => function (Options $options) {
-                    return ChoiceList::loader(
-                        // pass the instance of the type or type extension which is
-                        // currently configuring the choice list as first argument
-                        $this,
-                        // pass the other option to the loader
-                        new CustomChoiceLoader($options['some_key']),
-                        // ensure the type stores a loader per key
-                        // by using the special third argument "$vary"
-                        // an array containing anything that "changes" the loader
-                        [$options['some_key']]
-                    );
-                },
-            ]);
-        }
-    }
+the choice options would need to be resolved thus triggering the callback. When
+you're defining a custom choice type that may be reused in many fields (like
+entries of a collection) or reused in multiple forms at once, you should use the
+:class:`Symfony\\Component\\Form\\ChoiceList\\ChoiceList` static methods to wrap
+the loader and make the choice list cacheable for better performance:: //
+src/Form/ConstantsType.php namespace App\Form; use
+App\Form\ChoiceList\CustomChoiceLoader; use App\StaticClass; use
+Symfony\Component\Form\AbstractType; use
+Symfony\Component\Form\ChoiceList\ChoiceList; use
+Symfony\Component\Form\Extension\Core\Type\ChoiceType; use
+Symfony\Component\OptionsResolver\Options; use
+Symfony\Component\OptionsResolver\OptionsResolver; class ConstantsType extends
+AbstractType { public static function getExtendedTypes(): iterable { return
+[ChoiceType::class]; } public function configureOptions(OptionsResolver
+$resolver) { $resolver->setDefaults([ // the example below will create a
+CallbackChoiceLoader from the callable 'choice_loader' =>
+ChoiceList::lazy($this, function() { return StaticClass::getConstants(); }), //
+you can pass your own loader as well, depending on other options 'some_key' =>
+null, 'choice_loader' => function (Options $options) { return
+ChoiceList::loader( // pass the instance of the type or type extension which is
+// currently configuring the choice list as first argument $this, // pass the
+other option to the loader new CustomChoiceLoader($options['some_key']), //
+ensure the type stores a loader per key // by using the special third argument
+"$vary" // an array containing anything that "changes" the loader
+[$options['some_key']] ); }, ]); } }
