Fix all invalid API doc links

Author: wouterj

book/controller.rst

@@ -429,9 +429,7 @@ A great way to see the core functionality in action is to look in the
 Redirecting
 ~~~~~~~~~~~
 
-If you want to redirect the user to another page, use the
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::redirect`
-method::
+If you want to redirect the user to another page, use the ``redirect()`` method::
 
     public function indexAction()
     {
@@ -750,10 +748,9 @@ Forwarding to Another Controller
 --------------------------------
 
 Though not very common, you can also forward to another controller internally
-with the :method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::forward`
-method. Instead of redirecting the user's browser, it makes an internal sub-request,
-and calls the controller. The ``forward()`` method returns the ``Response``
-object that's returned from *that* controller::
+with the ``forward()`` method. Instead of redirecting the user's browser, it
+makes an internal sub-request, and calls the controller. The ``forward()``
+method returns the ``Response`` object that's returned from *that* controller::
 
     public function indexAction($name)
     {

book/doctrine.rst

@@ -519,11 +519,10 @@ of the bundle::
 .. tip::
 
     This article shows working with Doctrine from within a controller by using
-    the :method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::getDoctrine`
-    method of the controller. This method is a shortcut to get the
-    ``doctrine`` service. You can work with Doctrine anywhere else
-    by injecting that service in the service. See
-    :doc:`/book/service_container` for more on creating your own services.
+    the ``getDoctrine()`` method of the controller. This method is a shortcut
+    to get the ``doctrine`` service. You can work with Doctrine anywhere else
+    by injecting that service in the service. See :doc:`/book/service_container`
+    for more on creating your own services.
 
 Take a look at the previous example in more detail:
 

book/http_cache.rst

@@ -181,8 +181,7 @@ from your application and returning them to the client.
         error_log($kernel->getLog());
 
 The ``AppCache`` object has a sensible default configuration, but it can be
-finely tuned via a set of options you can set by overriding the
-:method:`Symfony\\Bundle\\FrameworkBundle\\HttpCache\\HttpCache::getOptions`
+finely tuned via a set of options you can set by overriding the ``getOptions()``
 method::
 
     // app/AppCache.php
@@ -627,7 +626,7 @@ doing so much work.
 
     Symfony also supports weak ETags by passing ``true`` as the second
     argument to the
-    :method:`Symfony\\Component\\HttpFoundation\\Response::setETag` method.
+    :method:`Symfony\\Component\\HttpFoundation\\Response::setEtag` method.
 
 .. index::
    single: Cache; Last-Modified header

components/config/definition.rst

@@ -117,9 +117,9 @@ Numeric Node Constraints
     The numeric (float and integer) nodes were introduced in Symfony 2.2.
 
 Numeric nodes (float and integer) provide two extra constraints -
-:method:`Symfony\\Component\\Config\\Definition\\Builder::min` and
-:method:`Symfony\\Component\\Config\\Definition\\Builder::max` -
-allowing to validate the value::
+:method:`Symfony\\Component\\Config\\Definition\\Builder\\IntegerNodeDefinition::min`
+and :method:`Symfony\\Component\\Config\\Definition\\Builder\\IntegerNodeDefinition::max`
+- allowing to validate the value::
 
     $rootNode
         ->children()

components/dom_crawler.rst

@@ -188,7 +188,7 @@ The crawler supports multiple ways of adding the content::
 .. note::
 
     When dealing with character sets other than ISO-8859-1, always add HTML
-    content using the :method:`Symfony\\Component\\DomCrawler\\Crawler::addHTMLContent`
+    content using the :method:`Symfony\\Component\\DomCrawler\\Crawler::addHtmlContent`
     method where you can specify the second parameter to be your target character
     set.
 

components/form/introduction.rst

@@ -379,9 +379,8 @@ Creating a simple Form
 
     If you're using the Symfony Framework, then the form factory is available
     automatically as a service called ``form.factory``. Also, the default
-    base controller class has a :method:`Symfony\\Bundle\\FrameworkBundle\\Controller::createFormBuilder`
-    method, which is a shortcut to fetch the form factory and call ``createBuilder``
-    on it.
+    base controller class has a ``createFormBuilder()`` method, which is a
+    shortcut to fetch the form factory and call ``createBuilder`` on it.
 
 Creating a form is done via a :class:`Symfony\\Component\\Form\\FormBuilder`
 object, where you build and configure different fields. The form builder

components/http_foundation/session_testing.rst

@@ -21,16 +21,16 @@ The mock storage drivers do not read or write the system globals
 ``session_id()`` or ``session_name()``. Methods are provided to simulate this if
 required:
 
-* :method:`Symfony\\Component\\HttpFoundation\\Session\\SessionStorageInterface::getId`: Gets the
+* :method:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\SessionStorageInterface::getId`: Gets the
   session ID.
 
-* :method:`Symfony\\Component\\HttpFoundation\\Session\\SessionStorageInterface::setId`: Sets the
+* :method:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\SessionStorageInterface::setId`: Sets the
   session ID.
 
-* :method:`Symfony\\Component\\HttpFoundation\\Session\\SessionStorageInterface::getName`: Gets the
+* :method:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\SessionStorageInterface::getName`: Gets the
   session name.
 
-* :method:`Symfony\\Component\\HttpFoundation\\Session\\SessionStorageInterface::setName`: Sets the
+* :method:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\SessionStorageInterface::setName`: Sets the
   session name.
 
 Unit Testing

components/http_foundation/sessions.rst

@@ -226,9 +226,6 @@ has a simple API
 :method:`Symfony\\Component\\HttpFoundation\\Session\\Attribute\\AttributeBagInterface::has`
     Returns true if the attribute exists.
 
-:method:`Symfony\\Component\\HttpFoundation\\Session\\Attribute\\AttributeBagInterface::keys`
-    Returns an array of stored attribute keys.
-
 :method:`Symfony\\Component\\HttpFoundation\\Session\\Attribute\\AttributeBagInterface::replace`
     Sets multiple attributes at once: takes a keyed array and sets each key => value pair.
 

components/process.rst

@@ -158,7 +158,7 @@ To make your code work better on all platforms, you might want to use the
     method was introduced in Symfony 2.3.
 
 In case you are building a binary driver, you can use the
-:method:`Symfony\\Component\\Process\\Process::setPrefix` method to prefix all
+:method:`Symfony\\Component\\Process\\ProcessBuilder::setPrefix` method to prefix all
 the generated process commands.
 
 The following example will generate two process commands for a tar binary
@@ -194,7 +194,7 @@ timeout (in seconds)::
     $process->run();
 
 If the timeout is reached, a
-:class:`Symfony\\Process\\Exception\\RuntimeException` is thrown.
+:class:`Symfony\\Component\\Process\\Exception\\RuntimeException` is thrown.
 
 For long running commands, it is your responsibility to perform the timeout
 check regularly::

components/security/authentication.rst

@@ -101,7 +101,7 @@ Each provider (since it implements
 has a method :method:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::supports`
 by which the ``AuthenticationProviderManager``
 can determine if it supports the given token. If this is the case, the
-manager then calls the provider's method :class:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::authenticate`.
+manager then calls the provider's method :method:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::authenticate`.
 This method should return an authenticated token or throw an
 :class:`Symfony\\Component\\Security\\Core\\Exception\\AuthenticationException`
 (or any other exception extending it).
@@ -204,8 +204,7 @@ own, it just needs to follow these rules:
    :method:`Symfony\\Component\\Security\\Core\\Encoder\\PasswordEncoderInterface::isPasswordValid`
    must first of all make sure the password is not too long, i.e. the password length is no longer
    than 4096 characters. This is for security reasons (see `CVE-2013-5750`_), and you can use the
-   :method:`Symfony\\Component\\Security\\Core\\Encoder\\BasePasswordEncoder::isPasswordTooLong`
-   method for this check::
+   ``isPasswordTooLong()`` method for this check::
 
        use Symfony\Component\Security\Core\Encoder\BasePasswordEncoder;
        use Symfony\Component\Security\Core\Exception\BadCredentialsException;

components/security/authorization.rst

@@ -177,7 +177,7 @@ Roles
 
 Roles are objects that give expression to a certain right the user has.
 The only requirement is that they implement :class:`Symfony\\Component\\Security\\Core\\Role\\RoleInterface`,
-which means they should also have a :method:`Symfony\\Component\\Security\\Core\\Role\\Role\\RoleInterface::getRole`
+which means they should also have a :method:`Symfony\\Component\\Security\\Core\\Role\\RoleInterface::getRole`
 method that returns a string representation of the role itself. The default
 :class:`Symfony\\Component\\Security\\Core\\Role\\Role` simply returns its
 first constructor argument::

components/translation/custom_formats.rst

@@ -102,12 +102,11 @@ will save a few lines::
         }
     }
 
-The :method:`Symfony\\Component\\Translation\\Dumper\\FileDumper::format`
-method creates the output string, that will be used by the
-:method:`Symfony\\Component\\Translation\\Dumper\\FileDumper::dump` method
-of the FileDumper class to create the file. The dumper can be used like any other
-built-in dumper. In the following example, the translation messages defined in the
-YAML file are dumped into a text file with the custom format::
+The ``format()`` method creates the output string, that will be used by the
+:method:`Symfony\\Component\\Translation\\Dumper\\FileDumper::dump` method of
+the FileDumper class to create the file. The dumper can be used like any other
+built-in dumper. In the following example, the translation messages defined in
+the YAML file are dumped into a text file with the custom format::
 
     use Symfony\Component\Translation\Loader\YamlFileLoader;
 

cookbook/bundles/configuration.rst

@@ -353,7 +353,7 @@ In order to use the schema, the XML configuration file must provide an
 ``xsi:schemaLocation`` attribute pointing to the XSD file for a certain XML
 namespace. This location always starts with the XML namespace. This XML
 namespace is then replaced with the XSD validation base path returned from
-:method:`Extension::getXsdValidationBasePath() <Symfony\\Component\\DependencyInjection\\ExtensionInterface::getXsdValidationBasePath>`
+:method:`Extension::getXsdValidationBasePath() <Symfony\\Component\\DependencyInjection\\Extension\\ExtensionInterface::getXsdValidationBasePath>`
 method. This namespace is then followed by the rest of the path from the base
 path to the file itself.
 

cookbook/controller/service.rst

@@ -240,22 +240,22 @@ Base Controller Methods and Their Service Replacements
 This list explains how to replace the convenience methods of the base
 controller:
 
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::createForm` (service: ``form.factory``)
+``createForm()`` (service: ``form.factory``)
     .. code-block:: php
 
         $formFactory->create($type, $data, $options);
 
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::createFormBuilder` (service: ``form.factory``)
+``createFormBuilder()`` (service: ``form.factory``)
     .. code-block:: php
 
         $formFactory->createBuilder('form', $data, $options);
 
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::createNotFoundException`
+``createNotFoundException()``
     .. code-block:: php
 
         new NotFoundHttpException($message, $previous);
 
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::forward` (service: ``http_kernel``)
+``forward()`` (service: ``http_kernel``)
     .. code-block:: php
 
         use Symfony\Component\HttpKernel\HttpKernelInterface;
@@ -266,16 +266,15 @@ controller:
         $subRequest = $request->duplicate($query, null, $attributes);
         $httpKernel->handle($subRequest, HttpKernelInterface::SUB_REQUEST);
 
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::generateUrl` (service: ``router``)
+``generateUrl()`` (service: ``router``)
     .. code-block:: php
 
        $router->generate($route, $params, $absolute);
 
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::getDoctrine` (service: ``doctrine``)
-
+``getDoctrine()`` (service: ``doctrine``)
     *Simply inject doctrine instead of fetching it from the container*
 
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::getUser` (service: ``security.context``)
+``getUser()`` (service: ``security.context``)
     .. code-block:: php
 
         $user = null;
@@ -284,29 +283,29 @@ controller:
              $user = $token->getUser();
         }
 
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::isGranted` (service: ``security.context``)
+``isGranted()`` (service: ``security.context``)
     .. code-block:: php
 
         $securityContext->isGranted($attributes, $object);
 
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::redirect`
+``redirect()``
     .. code-block:: php
 
         use Symfony\Component\HttpFoundation\RedirectResponse;
 
         return new RedirectResponse($url, $status);
 
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::render` (service: ``templating``)
+``render()`` (service: ``templating``)
     .. code-block:: php
 
         $templating->renderResponse($view, $parameters, $response);
 
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::renderView` (service: ``templating``)
+``renderView()`` (service: ``templating``)
     .. code-block:: php
 
        $templating->render($view, $parameters);
 
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::stream` (service: ``templating``)
+``stream()`` (service: ``templating``)
     .. code-block:: php
 
         use Symfony\Component\HttpFoundation\StreamedResponse;
@@ -324,7 +323,6 @@ controller:
     controller action method called ``Request $request``. The order of the
     parameters is not important, but the typehint must be provided.
 
-
 .. _`Controller class source code`: https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/Controller/Controller.php
 .. _`base Controller class`: https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/Controller/Controller.php
 .. _`FrameworkExtraBundle documentation`: https://symfony.com/doc/current/bundles/SensioFrameworkExtraBundle/annotations/routing.html

cookbook/controller/upload_file.rst

@@ -156,8 +156,9 @@ There are some important things to consider in the code of the above controller:
    provides methods for the most common operations when dealing with uploaded files.
 #. A well-known security best practice is to never trust the input provided by
    users. This also applies to the files uploaded by your visitors. The ``Uploaded``
-   class provides methods to get the original file extension (:method:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile::getExtension`),
-   the original file size (:method:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile::getSize`)
+   class provides methods to get the original file extension
+   (:method:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile::getExtension`),
+   the original file size (:method:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile::getClientSize`)
    and the original file name (:method:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile::getClientOriginalName`).
    However, they are considered *not safe* because a malicious user could tamper
    that information. That's why it's always better to generate a unique name and

cookbook/routing/redirect_in_config.rst

@@ -17,7 +17,7 @@ Redirecting Using a Path
 
 Assume there is no default controller for the ``/`` path of your application
 and you want to redirect these requests to ``/app``. You will need to use the
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\RedirectController::urlRedirect`
+:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\RedirectController::urlRedirectAction`
 action to redirect to this new url:
 
 .. configuration-block::
@@ -97,7 +97,7 @@ Redirecting Using a Route
 Assume you are migrating your website from WordPress to Symfony, you want to
 redirect ``/wp-admin`` to the route ``sonata_admin_dashboard``. You don't know
 the path, only the route name. This can be achieved using the
-:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\RedirectController::redirect`
+:method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\RedirectController::redirectAction`
 action:
 
 .. configuration-block::

reference/configuration/framework.rst

@@ -311,7 +311,7 @@ instance), the host might have been manipulated by an attacker.
     You can read "`HTTP Host header attacks`_" for more information about
     these kinds of attacks.
 
-The Symfony :method:`Request::getHost() <Symfony\\Component\\HttpFoundation\\Request:getHost>`
+The Symfony :method:`Request::getHost() <Symfony\\Component\\HttpFoundation\\Request::getHost>`
 method might be vulnerable to some of these attacks because it depends on
 the configuration of your web server. One simple solution to avoid these
 attacks is to whitelist the hosts that your Symfony application can respond