Merge remote-tracking branch 'upstream/7.3' into 7.3

* upstream/7.3:
  Add a few words about core team member responsibilities
  Fix 2 small grammar errors/6.4
  [Validator] Add support for the `otherwise` option in the `When` constraint
  [Mailer] Minor reformating
  Minor tweak
  [Frontend] Correct "Removes comments from CSS" comparison
  [symfony#20337] fix typo

Author: OskarStark

contributing/code/core_team.rst

@@ -13,15 +13,25 @@ This document states the rules that govern the Symfony core team. These rules
 are effective upon publication of this document and all Symfony Core members
 must adhere to said rules and protocol.
 
-Role of a Core Team Member
---------------------------
+Core Team Member Role
+---------------------
 
 In addition to being a regular contributor, core team members are expected to:
 
 * Review, approve, and merge pull requests;
 * Help enforce, improve, and implement Symfony :doc:`processes and policies </contributing/index>`;
 * Participate in the Symfony Core Team discussions (on Slack and GitHub).
 
+Core Team Member Responsibilities
+---------------------------------
+
+Core Team members are unpaid volunteers and as such, they are not expected to
+dedicate any specific amount of time on Symfony. They are expected to help the
+project in any way they can, from reviewing pull requests, writing documentation
+to participating in discussions and helping the community in general, but their
+involvement is completely voluntary and can be as much or as little as they
+want.
+
 Core Organization
 -----------------
 

doctrine/events.rst

@@ -3,7 +3,7 @@ Doctrine Events
 
 `Doctrine`_, the set of PHP libraries used by Symfony to work with databases,
 provides a lightweight event system to update entities during the application
-execution. These events, called `lifecycle events`_, allow to perform tasks such
+execution. These events, called `lifecycle events`_, allow performing tasks such
 as *"update the createdAt property automatically right before persisting entities
 of this type"*.
 
@@ -24,7 +24,7 @@ There are different ways to listen to these Doctrine events:
   methods are called for all entities, not only those of a certain type. They are
   ideal to **share event logic between entities**.
 
-The performance of each type of listener depends on how many entities applies to:
+The performance of each type of listener depends on how many entities it applies to:
 lifecycle callbacks are faster than entity listeners, which in turn are faster
 than lifecycle listeners.
 

frontend.rst

@@ -35,7 +35,7 @@ Supports Sass/Tailwind            :ref:`yes <asset-mapper-tailwind>`  yes
 Supports React, Vue, Svelte?      yes :ref:`[1] <ux-note-1>`          yes
 Supports TypeScript               :ref:`yes <asset-mapper-ts>`        yes
 Removes comments from JavaScript  no :ref:`[2] <ux-note-2>`           yes
-Removes comments from CSS         no :ref:`[2] <ux-note-2>`           no
+Removes comments from CSS         no :ref:`[2] <ux-note-2>`           yes :ref:`[4] <ux-note-4>`
 Versioned assets                  always                              optional
 Can update 3rd party packages     yes                                 no :ref:`[3] <ux-note-3>`
 ================================  ==================================  ==========
@@ -56,6 +56,11 @@ be executed by a browser.
 
 **[3]** If you use ``npm``, there are update checkers available (e.g. ``npm-check``).
 
+.. _ux-note-4:
+
+**[4]** CSS comments can be removed using `CssMinimizerPlugin`_, which is included
+in Webpack Encore and configurable via ``Encore.configureCssMinimizerPlugin()``.
+
 .. _frontend-asset-mapper:
 
 AssetMapper (Recommended)
@@ -153,3 +158,4 @@ Other Front-End Articles
 .. _`SensioLabs Minify Bundle`: https://github.com/sensiolabs/minify-bundle
 .. _`AssetMapper screencast series`: https://symfonycasts.com/screencast/asset-mapper
 .. _`API Platform screencast series`: https://symfonycasts.com/screencast/api-platform
+.. _`CssMinimizerPlugin`: https://webpack.js.org/plugins/css-minimizer-webpack-plugin

mailer.rst

@@ -661,8 +661,8 @@ header, etc.) but most of the times you'll set text headers::
 
     $email = (new Email())
         ->getHeaders()
-            // this non-standard header tells compliant autoresponders ("email holiday mode") to not
-            // reply to this message because it's an automated email
+            // this non-standard header tells compliant autoresponders ("email holiday mode")
+            // to not reply to this message because it's an automated email
             ->addTextHeader('X-Auto-Response-Suppress', 'OOF, DR, RN, NRN, AutoReply')
 
             // use an array if you want to add a header with multiple values

messenger.rst

@@ -2937,7 +2937,7 @@ and a different instance will be created per bus.
 .. tip::
 
     If you have installed the MakerBundle, you can use the ``make:messenger-middleware``
-    command to bootstrap the creation your own messenger middleware.
+    command to bootstrap the creation of your own messenger middleware.
 
 .. _middleware-doctrine:
 

reference/constraints/When.rst

@@ -9,6 +9,7 @@ Applies to  :ref:`class <validation-class-target>`
             or :ref:`property/method <validation-property-target>`
 Options     - `expression`_
             - `constraints`_
+            _ `otherwise`_
             - `groups`_
             - `payload`_
             - `values`_
@@ -47,7 +48,7 @@ properties::
 To validate the object, you have some requirements:
 
 A) If ``type`` is ``percent``, then ``value`` must be less than or equal 100;
-B) If ``type`` is ``absolute``, then ``value`` can be anything;
+B) If ``type`` is not ``percent``, then ``value`` must be less than 9999;
 C) No matter the value of ``type``, the ``value`` must be greater than 0.
 
 One way to accomplish this is with the When constraint:
@@ -69,6 +70,9 @@ One way to accomplish this is with the When constraint:
                 constraints: [
                     new Assert\LessThanOrEqual(100, message: 'The value should be between 1 and 100!')
                 ],
+                otherwise: [
+                    new Assert\LessThan(9999, message: 'The value should be less than 9999!')
+                ],
             )]
             private ?int $value;
 
@@ -88,6 +92,10 @@ One way to accomplish this is with the When constraint:
                             - LessThanOrEqual:
                                 value: 100
                                 message: "The value should be between 1 and 100!"
+                        otherwise:
+                            - LessThan:
+                                value: 9999
+                                message: "The value should be less than 9999!"
 
     .. code-block:: xml
 
@@ -109,6 +117,12 @@ One way to accomplish this is with the When constraint:
                                 <option name="message">The value should be between 1 and 100!</option>
                             </constraint>
                         </option>
+                        <option name="otherwise">
+                            <constraint name="LessThan">
+                                <option name="value">9999</option>
+                                <option name="message">The value should be less than 9999!</option>
+                            </constraint>
+                        </option>
                     </constraint>
                 </property>
             </class>
@@ -135,6 +149,12 @@ One way to accomplish this is with the When constraint:
                             message: 'The value should be between 1 and 100!',
                         ),
                     ],
+                    otherwise: [
+                        new Assert\LessThan(
+                            value: 9999,
+                            message: 'The value should be less than 9999!',
+                        ),
+                    ],
                 ));
             }
 
@@ -279,6 +299,17 @@ You can also pass custom variables using the `values`_ option.
 
 One or multiple constraints that are applied if the expression returns true.
 
+``otherwise``
+~~~~~~~~~~~~~
+
+**type**: ``array|Constraint``
+
+One or multiple constraints that are applied if the expression returns false.
+
+.. versionadded:: 7.3
+
+    The ``otherwise`` option was introduced in Symfony 7.3.
+
 .. include:: /reference/constraints/_groups-option.rst.inc
 
 .. include:: /reference/constraints/_payload-option.rst.inc