Use PHP 5.5's ::class notation

Author: wouterj

_includes/service_container/_my_mailer.rst.inc

@@ -27,9 +27,10 @@
     .. code-block:: php
 
         // app/config/services.php
+        use AppBundle\Mailer;
         use Symfony\Component\DependencyInjection\Definition;
 
         $container->setDefinition('app.mailer', new Definition(
-            'AppBundle\Mailer',
+            Mailer::class,
             array('sendmail')
         ));

best_practices/forms.rst

@@ -19,6 +19,7 @@ form in its own PHP class::
 
     namespace AppBundle\Form;
 
+    use AppBundle\Entity\Post;
     use Symfony\Component\Form\AbstractType;
     use Symfony\Component\Form\FormBuilderInterface;
     use Symfony\Component\OptionsResolver\OptionsResolver;
@@ -39,7 +40,7 @@ form in its own PHP class::
         public function configureOptions(OptionsResolver $resolver)
         {
             $resolver->setDefaults(array(
-                'data_class' => 'AppBundle\Entity\Post'
+                'data_class' => Post::class,
             ));
         }
 

bundles/extension.rst

@@ -137,14 +137,17 @@ Your bundles can also add their own classes into this file thanks to the
 ``addClassesToCompile()`` method. Define the classes to compile as an array of
 their fully qualified class names::
 
+    use AppBundle\Manager\UserManager;
+    use AppBundle\Utils\Slugger;
+
     // ...
     public function load(array $configs, ContainerBuilder $container)
     {
         // ...
 
         $this->addClassesToCompile(array(
-            'AppBundle\\Manager\\UserManager',
-            'AppBundle\\Utils\\Slugger',
+            UserManager::class,
+            Slugger::class,
             // ...
         ));
     }

bundles/override.rst

@@ -45,6 +45,7 @@ example, the implementing class for the ``original-service-id`` is changed to
     // src/Acme/DemoBundle/DependencyInjection/Compiler/OverrideServiceCompilerPass.php
     namespace Acme\DemoBundle\DependencyInjection\Compiler;
 
+    use Acme\DemoBundle\YourService;
     use Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface;
     use Symfony\Component\DependencyInjection\ContainerBuilder;
 
@@ -53,7 +54,7 @@ example, the implementing class for the ``original-service-id`` is changed to
         public function process(ContainerBuilder $container)
         {
             $definition = $container->getDefinition('original-service-id');
-            $definition->setClass('Acme\DemoBundle\YourService');
+            $definition->setClass(YourService::class);
         }
     }
 

components/class_loader/class_loader.rst

@@ -59,10 +59,10 @@ looked for in a location list to ease the vendoring of a sub-set of classes
 for large projects::
 
     $loader->addPrefixes(array(
-        'Doctrine\\Common'           => __DIR__.'/vendor/doctrine/common/lib',
-        'Doctrine\\DBAL\\Migrations' => __DIR__.'/vendor/doctrine/migrations/lib',
-        'Doctrine\\DBAL'             => __DIR__.'/vendor/doctrine/dbal/lib',
-        'Doctrine'                   => __DIR__.'/vendor/doctrine/orm/lib',
+        'Doctrine\Common'          => __DIR__.'/vendor/doctrine/common/lib',
+        'Doctrine\DBAL\Migrations' => __DIR__.'/vendor/doctrine/migrations/lib',
+        'Doctrine\DBAL'            => __DIR__.'/vendor/doctrine/dbal/lib',
+        'Doctrine'                 => __DIR__.'/vendor/doctrine/orm/lib',
     ));
 
 In this example, if you try to use a class in the ``Doctrine\Common`` namespace

components/class_loader/psr4_class_loader.rst

@@ -38,17 +38,15 @@ The directory structure will look like this:
     demo.php
 
 In ``demo.php`` you are going to parse the ``config.yml`` file. To do that, you
-first need to configure the ``Psr4ClassLoader``:
-
-.. code-block:: php
+first need to configure the ``Psr4ClassLoader``::
 
     use Symfony\Component\ClassLoader\Psr4ClassLoader;
     use Symfony\Component\Yaml\Yaml;
 
     require __DIR__.'/lib/ClassLoader/Psr4ClassLoader.php';
 
     $loader = new Psr4ClassLoader();
-    $loader->addPrefix('Symfony\\Component\\Yaml\\', __DIR__.'/lib/Yaml');
+    $loader->addPrefix('Symfony\Component\Yaml\\', __DIR__.'/lib/Yaml');
     $loader->register();
 
     $data = Yaml::parse(file_get_contents(__DIR__.'/config.yml'));

components/event_dispatcher.rst

@@ -201,27 +201,28 @@ determine which instance is passed.
         use Symfony\Component\DependencyInjection\Definition;
         use Symfony\Component\DependencyInjection\ParameterBag\ParameterBag;
         use Symfony\Component\DependencyInjection\Reference;
+        use Symfony\Component\EventDispatcher\ContainerAwareEventDispatcher;
         use Symfony\Component\EventDispatcher\DependencyInjection\RegisterListenersPass;
 
         $containerBuilder = new ContainerBuilder(new ParameterBag());
         $containerBuilder->addCompilerPass(new RegisterListenersPass());
 
         // register the event dispatcher service
         $containerBuilder->setDefinition('event_dispatcher', new Definition(
-            'Symfony\Component\EventDispatcher\ContainerAwareEventDispatcher',
+            ContainerAwareEventDispatcher::class,
             array(new Reference('service_container'))
         ));
 
         // register your event listener service
-        $listener = new Definition('AcmeListener');
+        $listener = new Definition(\AcmeListener::class);
         $listener->addTag('kernel.event_listener', array(
             'event' => 'foo.action',
             'method' => 'onFooAction',
         ));
         $containerBuilder->setDefinition('listener_service_id', $listener);
 
         // register an event subscriber
-        $subscriber = new Definition('AcmeSubscriber');
+        $subscriber = new Definition(\AcmeSubscriber::class);
         $subscriber->addTag('kernel.event_subscriber');
         $containerBuilder->setDefinition('subscriber_service_id', $subscriber);
 

components/form.rst

@@ -621,7 +621,7 @@ option when building each field:
             ->add('dueDate', 'date', array(
                 'constraints' => array(
                     new NotBlank(),
-                    new Type('\DateTime'),
+                    new Type(\DateTime::class),
                 )
             ))
             ->getForm();
@@ -638,7 +638,7 @@ option when building each field:
             ->add('dueDate', 'date', array(
                 'constraints' => array(
                     new NotBlank(),
-                    new Type('\DateTime'),
+                    new Type(\DateTime::class),
                 )
             ))
             ->getForm();

components/security/authentication.rst

@@ -177,19 +177,19 @@ user. This allows you to use different encoding strategies for different
 types of users. The default :class:`Symfony\\Component\\Security\\Core\\Encoder\\EncoderFactory`
 receives an array of encoders::
 
+    use Acme\Entity\LegacyUser;
     use Symfony\Component\Security\Core\Encoder\EncoderFactory;
     use Symfony\Component\Security\Core\Encoder\MessageDigestPasswordEncoder;
+    use Symfony\Component\Security\Core\User\User;
 
     $defaultEncoder = new MessageDigestPasswordEncoder('sha512', true, 5000);
     $weakEncoder = new MessageDigestPasswordEncoder('md5', true, 1);
 
     $encoders = array(
-        'Symfony\\Component\\Security\\Core\\User\\User' => $defaultEncoder,
-        'Acme\\Entity\\LegacyUser'                       => $weakEncoder,
-
+        User::class       => $defaultEncoder,
+        LegacyUser::class => $weakEncoder,
         // ...
     );
-
     $encoderFactory = new EncoderFactory($encoders);
 
 Each encoder should implement :class:`Symfony\\Component\\Security\\Core\\Encoder\\PasswordEncoderInterface`

components/security/authorization.rst

@@ -118,9 +118,11 @@ on a "remember-me" cookie, or even authenticated anonymously?
 .. code-block:: php
 
     use Symfony\Component\Security\Core\Authentication\AuthenticationTrustResolver;
+    use Symfony\Component\Security\Core\Authentication\Token\AnonymousToken;
+    use Symfony\Component\Security\Core\Authentication\Token\RememberMeToken;
 
-    $anonymousClass = 'Symfony\Component\Security\Core\Authentication\Token\AnonymousToken';
-    $rememberMeClass = 'Symfony\Component\Security\Core\Authentication\Token\RememberMeToken';
+    $anonymousClass = AnonymousToken::class;
+    $rememberMeClass = RememberMeToken::Class;
 
     $trustResolver = new AuthenticationTrustResolver($anonymousClass, $rememberMeClass);
 

components/serializer.rst

@@ -133,6 +133,8 @@ Deserializing an Object
 You'll now learn how to do the exact opposite. This time, the information
 of the ``Person`` class would be encoded in XML format::
 
+    use Acme\Person;
+
     $data = <<<EOF
     <person>
         <name>foo</name>
@@ -141,7 +143,7 @@ of the ``Person`` class would be encoded in XML format::
     </person>
     EOF;
 
-    $person = $serializer->deserialize($data, 'Acme\Person', 'xml');
+    $person = $serializer->deserialize($data, Person::class, 'xml');
 
 In this case, :method:`Symfony\\Component\\Serializer\\Serializer::deserialize`
 needs three parameters:
@@ -155,7 +157,8 @@ Deserializing in an Existing Object
 
 The serializer can also be used to update an existing object::
 
-    $person = new Acme\Person();
+    // ...
+    $person = new Person();
     $person->setName('bar');
     $person->setAge(99);
     $person->setSportsman(true);
@@ -167,7 +170,7 @@ The serializer can also be used to update an existing object::
     </person>
     EOF;
 
-    $serializer->deserialize($data, 'Acme\Person', 'xml', array('object_to_populate' => $person));
+    $serializer->deserialize($data, Person::class, 'xml', array('object_to_populate' => $person));
     // $person = Acme\Person(name: 'foo', age: '69', sportsman: true)
 
 This is a common need when working with an ORM.

console/commands_as_services.rst

@@ -52,11 +52,10 @@ with ``console.command``:
     .. code-block:: php
 
         // app/config/config.php
+        use AppBundle\Command\MyCommand;
+
         $container
-            ->register(
-                'app.command.my_command',
-                'AppBundle\Command\MyCommand'
-            )
+            ->register('app.command.my_command', MyCommand::class)
             ->addTag('console.command')
         ;
 
@@ -164,13 +163,12 @@ inject the ``command.default_name`` parameter:
     .. code-block:: php
 
         // app/config/config.php
+        use AppBundle\Command\MyCommand;
+
         $container->setParameter('command.default_name', 'Javier');
 
         $container
-            ->register(
-                'app.command.my_command',
-                'AppBundle\Command\MyCommand',
-            )
+            ->register('app.command.my_command', MyCommand::class)
             ->setArguments(array('%command.default_name%'))
             ->addTag('console.command')
         ;

console/logging.rst

@@ -109,11 +109,12 @@ First configure a listener for console exception events in the service container
     .. code-block:: php
 
         // app/config/services.php
+        use AppBundle\EventListener\ConsoleExceptionListener;
         use Symfony\Component\DependencyInjection\Definition;
         use Symfony\Component\DependencyInjection\Reference;
 
         $definitionConsoleExceptionListener = new Definition(
-            'AppBundle\EventListener\ConsoleExceptionListener',
+            ConsoleExceptionListener::class,
             array(new Reference('logger'))
         );
         $definitionConsoleExceptionListener->addTag(
@@ -206,11 +207,12 @@ First configure a listener for console terminate events in the service container
     .. code-block:: php
 
         // app/config/services.php
+        use AppBundle\EventListener\ErrorLoggerListener;
         use Symfony\Component\DependencyInjection\Definition;
         use Symfony\Component\DependencyInjection\Reference;
 
         $definitionErrorLoggerListener = new Definition(
-            'AppBundle\EventListener\ErrorLoggerListener',
+            ErrorLoggerListener::class,
             array(new Reference('logger'))
         );
         $definitionErrorLoggerListener->addTag(

controller/error_pages.rst

@@ -317,10 +317,11 @@ In that case, you might want to override one or both of the ``showAction()`` and
         .. code-block:: php
 
             // app/config/services.php
+            use AppBundle\Controller\CustomExceptionController;
             use Symfony\Component\DependencyInjection\Reference;
             use Symfony\Component\DependencyInjection\Definition;
 
-            $definition = new Definition('AppBundle\Controller\CustomExceptionController', array(
+            $definition = new Definition(CustomExceptionController::class, array(
                 new Reference('twig'),
                 '%kernel.debug%'
             ));

controller/service.rst

@@ -79,11 +79,9 @@ Then you can define it as a service as follows:
     .. code-block:: php
 
         // app/config/services.php
-        use Symfony\Component\DependencyInjection\Definition;
+        use AppBundle\Controller\HelloController;
 
-        $container->setDefinition('app.hello_controller', new Definition(
-            'AppBundle\Controller\HelloController'
-        ));
+        $container->register('app.hello_controller', HelloController::class);
 
 Referring to the Service
 ------------------------
@@ -230,11 +228,12 @@ argument:
     .. code-block:: php
 
         // app/config/services.php
+        use AppBundle\Controller\HelloController;
         use Symfony\Component\DependencyInjection\Definition;
         use Symfony\Component\DependencyInjection\Reference;
 
         $container->setDefinition('app.hello_controller', new Definition(
-            'AppBundle\Controller\HelloController',
+            HelloController::class,
             array(new Reference('templating'))
         ));
 

controller/soap_web_service.rst

@@ -77,8 +77,10 @@ a ``HelloService`` object properly:
     .. code-block:: php
 
         // app/config/services.php
+        use Acme\SoapBundle\Services\HelloService;
+
         $container
-            ->register('hello_service', 'Acme\SoapBundle\Services\HelloService')
+            ->register('hello_service', HelloService::class)
             ->addArgument(new Reference('mailer'));
 
 Below is an example of a controller that is capable of handling a SOAP

controller/upload_file.rst

@@ -54,6 +54,7 @@ Then, add a new ``brochure`` field to the form that manages the ``Product`` enti
     // src/AppBundle/Form/ProductType.php
     namespace AppBundle\Form;
 
+    use AppBundle\Entity\Product;
     use Symfony\Component\Form\AbstractType;
     use Symfony\Component\Form\FormBuilderInterface;
     use Symfony\Component\OptionsResolver\OptionsResolver;
@@ -72,7 +73,7 @@ Then, add a new ``brochure`` field to the form that manages the ``Product`` enti
         public function configureOptions(OptionsResolver $resolver)
         {
             $resolver->setDefaults(array(
-                'data_class' => 'AppBundle\Entity\Product',
+                'data_class' => Product::class,
             ));
         }
 
@@ -280,11 +281,12 @@ Then, define a service for this class:
     .. code-block:: php
 
         // app/config/services.php
+        use AppBundle\FileUploader;
         use Symfony\Component\DependencyInjection\Definition;
 
         // ...
         $container->setDefinition('app.brochure_uploader', new Definition(
-            'AppBundle\FileUploader',
+            FileUploader::class,
             array('%brochures_directory%')
         ));
 
@@ -407,11 +409,13 @@ Now, register this class as a Doctrine listener:
     .. code-block:: php
 
         // app/config/services.php
+        use AppBundle\EventListener\BrochureUploaderListener;
+        use Symfony\Component\DependencyInjection\Definition;
         use Symfony\Component\DependencyInjection\Reference;
 
         // ...
         $definition = new Definition(
-            'AppBundle\EventListener\BrochureUploaderListener',
+            BrochureUploaderListener::class,
             array(new Reference('brochures_directory'))
         );
         $definition->addTag('doctrine.event_listener', array(