Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Add information about resolver argument priority #14069

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
Sep 9, 2020
Merged

Add information about resolver argument priority #14069

merged 1 commit into from
Sep 9, 2020

Conversation

casahugo
Copy link
Contributor

controller/argument_value_resolver.rst Outdated Show resolved Hide resolved
Copy link
Contributor

@ogizanagi ogizanagi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for taking the time to improve this doc 👍

@@ -239,6 +239,7 @@ priority of 100. As this one is responsible for fetching attributes from the
lower priority. This makes sure the argument resolvers are not triggered when
the attribute is present. For instance, when passing the user along a
sub-requests.
However, if the injected parameter is an attribute of the request, it is necessary to set a priority of at least 100 otherwise the resolver will not be launched.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
However, if the injected parameter is an attribute of the request, it is necessary to set a priority of at least 100 otherwise the resolver will not be launched.
However, if the argument is resolved from a request attribute, it is necessary to set a priority of at least 100 otherwise the resolver will not be executed.

?

@xabbuh xabbuh linked an issue Aug 29, 2020 that may be closed by this pull request
@xabbuh xabbuh added this to the 4.4 milestone Aug 29, 2020
@javiereguiluz javiereguiluz changed the base branch from 5.1 to 4.4 September 9, 2020 18:43
@javiereguiluz javiereguiluz merged commit d45acbf into symfony:4.4 Sep 9, 2020
@javiereguiluz
Copy link
Member

Hugo, thanks for your contribution to help this description. While merging, we made more rewords because the original paragraph was a bit confusing, but we kept most of your contribution. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Custom ArgumentResolver priority
5 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.