8000 removed versionadded, fixed count and note which behaves like version… by OskarStark · Pull Request #11074 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

removed versionadded, fixed count and note which behaves like version… # 8000 11074

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 4, 2019
Merged

removed versionadded, fixed count and note which behaves like version… #11074

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 1 addition & 10 deletions controller/argument_value_resolver.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,11 +15,7 @@ functionality.
Functionality Shipped with the HttpKernel
-----------------------------------------

.. versionadded:: 3.3

The ``SessionValueResolver`` and ``ServiceValueResolver`` were both added in Symfony 3.3.

Symfony ships with five value resolvers in the HttpKernel component:
Symfony ships with the following value resolvers in the HttpKernel component:

:class:`Symfony\\Component\\HttpKernel\\Controller\\ArgumentResolver\\RequestAttributeValueResolver`
Attempts to find a request attribute that matches the name of the argument.
Expand All @@ -46,11 +42,6 @@ Symfony ships with five value resolvers in the HttpKernel component:
argument list. When the action is called, the last (variadic) argument will
contain all the values of this array.

.. note::

Prior to Symfony 3.1, this logic was resolved within the ``ControllerResolver``.
The old functionality is rewritten to the aforementioned value resolvers.

Adding a Custom Value Resolver
------------------------------

Expand Down
0