@@ -18,17 +18,17 @@ Functionality Shipped With The HttpKernel
18
18
19
19
Symfony ships with four value resolvers in the HttpKernel:
20
20
* The :class: `Symfony\\ Component\\ HttpKernel\\ Controller\\ ArgumentValueResolver\\ ArgumentFromAttributeResolver `
21
- attempts to find a request attribute that matches the name of the argument.
21
+ attempts to find a request attribute that matches the name of the argument.
22
22
23
23
* The :class: `Symfony\\ Component\\ HttpKernel\\ Controller\\ ArgumentValueResolver\\ RequestValueResolver `
24
- injects the current ``Request `` if type-hinted with ``Request ``, or a sub-class thereof.
24
+ injects the current ``Request `` if type-hinted with ``Request ``, or a sub-class thereof.
25
25
26
26
* The :class: `Symfony\\ Component\\ HttpKernel\\ Controller\\ ArgumentValueResolver\\ DefaultValueResolver `
27
- will set the default value of the argument if present and the argument is optional.
27
+ will set the default value of the argument if present and the argument is optional.
28
28
29
29
* The :class: `Symfony\\ Component\\ HttpKernel\\ Controller\\ ArgumentValueResolver\\ VariadicValueResolver `
30
- verifies in the request if your data is an array and will add all of them to the argument list.
31
- When the action is called, the last (variadic) argument will contain all the values of this array.
30
+ verifies in the request if your data is an array and will add all of them to the argument list.
31
+ When the action is called, the last (variadic) argument will contain all the values of this array.
32
32
33
33
.. note ::
34
34
@@ -64,16 +64,16 @@ This interface specifies that you have to implement two methods::
64
64
}
65
65
66
66
* The ``supports()`` method is used to check whether the resolver supports the given argument. It will
67
- only continue if it returns ``true``.
67
+ only continue if it returns ``true``.
68
68
69
69
* The ``resolve()`` method will be used to resolve the actual value just acknowledged by
70
- ``supports()``. Once a value is resolved you can ``yield`` the value to the ``ArgumentResolver``.
70
+ ``supports()``. Once a value is resolved you can ``yield`` the value to the ``ArgumentResolver``.
71
71
72
72
* The ``Request`` object is the current ``Request`` which would also be injected into your
73
- action in the forementioned functionality.
73
+ action in the forementioned functionality.
74
74
75
75
* The :class:``Symfony\\Component\\HttpKernel\\ControllerMetadata\\ArgumentMetadata`` represents
76
- information retrieved from the method signature for the current argument it's trying to resolve.
76
+ information retrieved from the method signature for the current argument it's trying to resolve.
77
77
78
78
.. note ::
79
79
0 commit comments