Skip to content

Commit eb6a274

Browse files
committed
Reword
1 parent d45acbf commit eb6a274

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

Diff for: controller/argument_value_resolver.rst

+6-7
Original file line numberDiff line numberDiff line change
@@ -244,13 +244,12 @@ and adding a priority.
244244
;
245245
246246
While adding a priority is optional, it's recommended to add one to make sure
247-
the expected value is injected. The ``RequestAttributeValueResolver`` has a
248-
priority of 100. As this one is responsible for fetching attributes from the
249-
``Request``, it's recommended to trigger your custom value resolver with a
250-
lower priority. This makes sure the argument resolvers are not triggered when
251-
the attribute is present. For instance, when passing the user along a
252-
sub-requests.
253-
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.
247+
the expected value is injected. The built-in ``RequestAttributeValueResolver``,
248+
which fetches attributes from the ``Request``, has a priority of ``100``. If your
249+
resolver also fetches ``Request`` attributes, set a priority of ``100`` or more.
250+
Otherwise, set a priority lower than ``100`` to make sure the argument resolver
251+
is not triggered when the ``Request`` attribute is present (for example, when
252+
passing the user along sub-requests).
254253

255254
.. tip::
256255

0 commit comments

Comments
 (0)