Do not hardcode priorities

symfony · javiereguiluz · Jun 15, 2023 · Feb 28, 2023 · Apr 21, 2023 · Jun 4, 2023
commit 1009ca2d7ca11133377b8f254841a3e92ed901ef
diff --git a/controller/value_resolver.rst b/controller/value_resolver.rst
@@ -218,8 +218,8 @@ Managing Value Resolvers

 For each argument, every resolver tagged with ``controller.argument_value_resolver``
 will be called until one provides a value. The order in which they are called depends
-on their priority. For example, the ``SessionValueResolver`` (priority 50) will be
-called before the ``DefaultValueResolver`` (priority -100) which allows to write e.g.
+on their priority. For example, the ``SessionValueResolver`` will be called before the
+``DefaultValueResolver`` because its priority is higher. This allows to write e.g.
 ``SessionInterface $session = null`` to get the session if there is one, or ``null``
 if there is none.