Skip to content

Add hint how to debug argument resolver order #16616

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.

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 21, 2022
Merged
Changes from all commits
Commits
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
7 changes: 7 additions & 0 deletions controller/argument_value_resolver.rst
Original file line number Diff line number Diff line change
Expand Up @@ -242,6 +242,13 @@ Otherwise, set a priority lower than ``100`` to make sure the argument resolver
is not triggered when the ``Request`` attribute is present (for example, when
passing the user along sub-requests).

To ensure your resolvers are added in the right position you can run the following
command to see which argument resolvers are present and in which order they run.

.. code-block:: terminal

$ php bin/console debug:container debug.argument_resolver.inner --show-arguments

.. tip::

As you can see in the ``UserValueResolver::supports()`` method, the user
Expand Down