Merge branch '6.3' into 6.4

* 6.3:
  Prefer placing services before query parameters
  [Console] Fix a typo after symfony#18739
  [Validator] add section for overridden properties

Author: javiereguiluz

console.rst

@@ -602,7 +602,7 @@ tools capable of helping you with different tasks:
 * :doc:`/components/console/helpers/table`: displays tabular data as a table
 * :doc:`/components/console/helpers/debug_formatter`: provides functions to
   output debug information when running an external program
-* :doc:`/components/console/helpers/processhelper`: allows to run processes using ``DebugProcessHelper``
+* :doc:`/components/console/helpers/processhelper`: allows to run processes using ``DebugFormatterHelper``
 * :doc:`/components/console/helpers/cursor`: allows to manipulate the cursor in the terminal
 
 .. _`exit status`: https://en.wikipedia.org/wiki/Exit_status

doctrine.rst

@@ -539,7 +539,7 @@ and injected by the dependency injection container::
     class ProductController extends AbstractController
     {
         #[Route('/product/{id}', name: 'product_show')]
-        public function show(int $id, ProductRepository $productRepository): Response
+        public function show(ProductRepository $productRepository, int $id): Response
         {
             $product = $productRepository
                 ->find($id);

validation.rst

@@ -638,6 +638,20 @@ constraint that's applied to the class itself. When that class is validated,
 methods specified by that constraint are simply executed so that each can
 provide more custom validation.
 
+Validating Object With Inheritance
+----------------------------------
+
+When you validate an object that extends another class, the validator
+automatically validates constraints defined in the parent class as well.
+
+**The constraints defined in the parent properties will be applied to the child
+properties even if the child properties override those constraints**. Symfony
+will always merge the parent constraints for each property.
+
+You can't change this behavior, but you can overcome it by defining the parent
+and the child contraints in different :doc:`validation groups </validation/groups>`
+and then select the appropriate group when validating each object.
+
 Debugging the Constraints
 -------------------------