Add missing imports and remove useless

components/console/helpers/questionhelper.rst

@@ -25,6 +25,7 @@ Suppose you want to confirm an action before actually executing it. Add
 the following to your command::
 
     // ...
+    use Symfony\Component\Console\Command\Command;
     use Symfony\Component\Console\Input\InputInterface;
     use Symfony\Component\Console\Output\OutputInterface;
     use Symfony\Component\Console\Question\ConfirmationQuestion;

components/console/helpers/table.rst

@@ -20,7 +20,10 @@ When building a console application it may be useful to display tabular data:
 To display a table, use :class:`Symfony\\Component\\Console\\Helper\\Table`,
 set the headers, set the rows and then render the table::
 
+    use Symfony\Component\Console\Command\Command;
     use Symfony\Component\Console\Helper\Table;
+    use Symfony\Component\Console\Input\InputInterface;
+    use Symfony\Component\Console\Output\OutputInterface;
     // ...
 
     class SomeCommand extends Command

console.rst

@@ -66,6 +66,10 @@ constructor. If your command defines its own constructor, set the properties
 first and then call to the parent constructor, to make those properties
 available in the ``configure()`` method::
 
+    // ...
+    use Symfony\Component\Console\Command\Command;
+    use Symfony\Component\Console\Input\InputArgument;
+
     class CreateUserCommand extends Command
     {
         // ...

console/calling_commands.rst

@@ -11,6 +11,8 @@ generating Doctrine2 proxies, dumping Assetic assets, ...).
 Calling a command from another one is straightforward::
 
     use Symfony\Component\Console\Input\ArrayInput;
+    use Symfony\Component\Console\Input\InputInterface;
+    use Symfony\Component\Console\Output\OutputInterface;
     // ...
 
     protected function execute(InputInterface $input, OutputInterface $output)

console/input.rst

@@ -14,6 +14,7 @@ or required. For example, to add an optional ``last_name`` argument to the comma
 and make the ``name`` argument required::
 
     // ...
+    use Symfony\Component\Console\Command\Command;
     use Symfony\Component\Console\Input\InputArgument;
 
     class GreetCommand extends Command
@@ -33,6 +34,10 @@ and make the ``name`` argument required::
 You now have access to a ``last_name`` argument in your command::
 
     // ...
+    use Symfony\Component\Console\Command\Command;
+    use Symfony\Component\Console\Input\InputInterface;
+    use Symfony\Component\Console\Output\OutputInterface;
+
     class GreetCommand extends Command
     {
         // ...

console/lockable_trait.rst

@@ -14,7 +14,10 @@ In addition, the Console component provides a PHP trait called ``LockableTrait``
 that adds two convenient methods to lock and release commands::
 
     // ...
+    use Symfony\Component\Console\Command\Command;
     use Symfony\Component\Console\Command\LockableTrait;
+    use Symfony\Component\Console\Input\InputInterface;
+    use Symfony\Component\Console\Output\OutputInterface;
 
     class UpdateContentsCommand extends Command
     {

console/verbosity.rst

@@ -41,6 +41,10 @@ It is possible to print a message in a command for only a specific verbosity
 level. For example::
 
     // ...
+    use Symfony\Component\Console\Command\Command;
+    use Symfony\Component\Console\Input\InputInterface;
+    use Symfony\Component\Console\Output\OutputInterface;
+
     class CreateUserCommand extends Command
     {
         // ...

event_dispatcher.rst

@@ -200,8 +200,6 @@ or a "sub request"::
     namespace AppBundle\EventListener;
 
     use Symfony\Component\HttpKernel\Event\GetResponseEvent;
-    use Symfony\Component\HttpKernel\HttpKernel;
-    use Symfony\Component\HttpKernel\HttpKernelInterface;
 
     class RequestListener
     {

http_cache/validation.rst

@@ -62,6 +62,7 @@ To see a simple implementation, generate the ETag as the md5 of the content::
     // src/AppBundle/Controller/DefaultController.php
     namespace AppBundle\Controller;
 
+    use Symfony\Bundle\FrameworkBundle\Controller\Controller;
     use Symfony\Component\HttpFoundation\Request;
 
     class DefaultController extends Controller

security/ldap.rst

@@ -100,7 +100,6 @@ An LDAP client can be simply configured using the built-in
         // app/config/services.php
         use Symfony\Component\Ldap\Ldap;
         use Symfony\Component\Ldap\Adapter\ExtLdap\Adapter;
-        use Symfony\Component\DependencyInjection\Definition;
 
         $container->register(Ldap::class)
             ->addArgument(new Reference(Adapter::class);

security/voters.rst

@@ -36,6 +36,9 @@ A custom voter needs to implement
 or extend :class:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\Voter`,
 which makes creating a voter even easier::
 
+    use Symfony\Component\Security\Core\Authentication\Token\TokenInterface;
+    use Symfony\Component\Security\Core\Authorization\Voter\VoterInterface;
+
     abstract class Voter implements VoterInterface
     {
         abstract protected function supports($attribute, $subject);

service_container/definitions.rst

@@ -21,6 +21,8 @@ Getting and Setting Service Definitions
 
 There are some helpful methods for working with the service definitions::
 
+    use Symfony\Component\DependencyInjection\Definition;
+
     // finds out if there is an "app.mailer" definition
     $container->hasDefinition('app.mailer');
     // finds out if there is an "app.mailer" definition or alias

service_container/factories.rst

@@ -142,6 +142,7 @@ Configuration of the service container then looks like this:
 
         use AppBundle\Email\NewsletterManager;
         use AppBundle\Email\NewsletterManagerFactory;
+        use Symfony\Component\DependencyInjection\Reference;
         // ...
 
         $container->register(NewsletterManagerFactory::class);

service_container/parent_services.rst

@@ -12,6 +12,9 @@ you may have multiple repository classes which need the
     // src/AppBundle/Repository/BaseDoctrineRepository.php
     namespace AppBundle\Repository;
 
+    use Doctrine\Common\Persistence\ObjectManager;
+    use Psr\Log\LoggerInterface;
+
     // ...
     abstract class BaseDoctrineRepository
     {

service_container/synthetic_services.rst

@@ -11,6 +11,9 @@ For instance, the ``kernel`` service in Symfony is injected into the container
 from within the ``Kernel`` class::
 
     // ...
+    use Symfony\Component\HttpKernel\KernelInterface;
+    use Symfony\Component\HttpKernel\TerminableInterface;
+
     abstract class Kernel implements KernelInterface, TerminableInterface
     {
         // ...

session/proxy_examples.rst

@@ -108,7 +108,6 @@ can intercept the session before it is written::
     // src/AppBundle/Session/ReadOnlySessionProxy.php
     namespace AppBundle\Session;
 
-    use AppBundle\Entity\User;
     use Symfony\Component\HttpFoundation\Session\Storage\Proxy\SessionHandlerProxy;
     use Symfony\Component\Security\Core\Security;
 

testing/insulating_clients.rst

@@ -8,6 +8,7 @@ If you need to simulate an interaction between different clients (think of a
 chat for instance), create several clients::
 
     // ...
+    use Symfony\Component\HttpFoundation\Response;
 
     $harry = static::createClient();
     $sally = static::createClient();
@@ -23,6 +24,7 @@ a third-party library that has some kind of global state. In such a case, you
 can insulate your clients::
 
     // ...
+    use Symfony\Component\HttpFoundation\Response;
 
     $harry = static::createClient();
     $sally = static::createClient();

testing/profiling.rst

@@ -15,6 +15,8 @@ spent in the framework, etc. But before writing assertions, enable the profiler
 and check that the profiler is indeed available (it is enabled by default in
 the ``test`` environment)::
 
+    use Symfony\Bundle\FrameworkBundle\Test\WebTestCase;
+
     class LuckyControllerTest extends WebTestCase
     {
         public function testNumberAction()

validation/sequence_provider.rst

@@ -142,8 +142,9 @@ that group are valid, the second group, ``Strict``, will be validated.
 
 You can also define a group sequence in the ``validation_groups`` form option::
 
-    use Symfony\Component\Validator\Constraints\GroupSequence;
     use Symfony\Component\Form\AbstractType;
+    use Symfony\Component\OptionsResolver\OptionsResolver;
+    use Symfony\Component\Validator\Constraints\GroupSequence;
     // ...
 
     class MyType extends AbstractType