8000 minor #12945 Move method and class (OskarStark) · symfony/symfony-docs@0c91dfc · GitHub
[go: up one dir, main page]
Skip to content

Commit 0c91dfc

Browse files
OskarStarkOskarStark
committed
minor #12945 Move method and class (OskarStark)
This PR was merged into the 3.4 branch. Discussion ---------- Move method and class It reads more natural to me. I would check the following branches if you agree and in this case we could add a Doctor rule. Cheers Commits ------- 8bffa06 Move method and class
2 parents afdb2c6 + 8bffa06 commit 0c91dfc

File tree

7 files changed

+8
-8
lines changed

7 files changed

+8
-8
lines changed

‎components/console/single_command_tool.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ it is possible to remove this need by declaring a single command application::
2929
->setDefaultCommand('echo', true) // Single command application
3030
->run();
3131

32-
The method :method:`Symfony\\Component\\Console\\Application::setDefaultCommand`
32+
The :method:`Symfony\\Component\\Console\\Application::setDefaultCommand` method
3333
accepts a boolean as second parameter. If true, the command ``echo`` will then
3434
always be used, without having to pass its name.
3535

‎components/options_resolver.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -297,7 +297,7 @@ been set::
297297
}
298298
}
299299

300-
The method :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::getMissingOptions`
300+
The :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::getMissingOptions` method
301301
lets you access the names of all missing options.
302302

303303
Type Validation

‎components/routing.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Usage
2828

2929
In order to set up a basic routing system you need three parts:
3030

31-
* A :class:`Symfony\\Component\\Routing\\RouteCollection`, which contains the route definitions (instances of the class :class:`Symfony\\Component\\Routing\\Route`)
31+
* A :class:`Symfony\\Component\\Routing\\RouteCollection`, which contains the route definitions (instances of the :class:`Symfony\\Component\\Routing\\Route` class)
3232
* A :class:`Symfony\\Component\\Routing\\RequestContext`, which has information about the request
3333
* A :class:`Symfony\\Component\\Routing\\Matcher\\UrlMatcher`, which performs the mapping of the request to a single route
3434

‎components/security/authentication.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,10 +100,10 @@ Authentication Providers
100100

101101
Each provider (since it implements
102102
:class:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface`)
103-
has a method :method:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::supports`
103+
has a :method:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::supports` method
104104
by which the ``AuthenticationProviderManager``
105105
can determine if it supports the given token. If this is the case, the
106-
manager then calls the provider's method :method:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::authenticate`.
106+
manager then calls the provider's :method:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::authenticate` method.
107107
This method should return an authenticated token or throw an
108108
:class:`Symfony\\Component\\Security\\Core\\Exception\\AuthenticationException`
109109
(or any other exception extending it).

‎reference/constraints/File.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Validates that a value is a valid "file", which can be one of the following:
66
* A string (or object with a ``__toString()`` method) path to an existing
77
file;
88
* A valid :class:`Symfony\\Component\\HttpFoundation\\File\\File` object
9-
(including objects of class :class:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile`).
9+
(including objects of :class:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile` class).
1010

1111
This constraint is commonly used in forms with the :doc:`FileType </reference/forms/types/file>`
1212
form field.

‎validation.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -115,7 +115,7 @@ on the ``validator`` service (which implements :class:`Symfony\\Component\\Valid
115115
The job of the ``validator`` is easy: to read the constraints (i.e. rules)
116116
of a class and verify if the data on the object satisfies those
117117
constraints. If validation fails, a non-empty list of errors
118-
(class :class:`Symfony\\Component\\Validator\\ConstraintViolationList`) is
118+
(:class:`Symfony\\Component\\Validator\\ConstraintViolationList` class) is
119119
returned. Take this simple example from inside a controller::
120120

121121
// ...

‎workflow.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -391,7 +391,7 @@ This means that each event has access to the following information:
391391

392392
The ``getWorkflowName()`` method was introduced in Symfony 3.3.
393393

394-
For Guard Events, there is an extended class :class:`Symfony\\Component\\Workflow\\Event\\GuardEvent`.
394+
For Guard Events, there is an extended :class:`Symfony\\Component\\Workflow\\Event\\GuardEvent` class.
395395
This class has two more methods:
396396

397397
:method:`Symfony\\Component\\Workflow\\Event\\GuardEvent::isBlocked`

0 commit comments

Comments
 (0)
0