Merge branch '7.1' into 7.2

* 7.1:
  [Notifier] Add a missing reference link
  Use Doctor RST 1.61.1
  implement __isset() together with __get()
  Fix some merging issues
  Minor tweaks
  Add extra information on AsEventListener attribute usage
  [HttpCache] Remove SensioFrameworkExtraBundle reference
  [AssetMapper] Remove Cloudflare auto-minify links
  [Notifier] Change the structure of the table listing the notifiers
  [Reference] Replace param converter with value resolver

Author: javiereguiluz

.doctor-rst.yaml

@@ -29,6 +29,7 @@ rules:
         max: 2
     max_colons: ~
     no_app_console: ~
+    no_attribute_redundant_parenthesis: ~
     no_blank_line_after_filepath_in_php_code_block: ~
     no_blank_line_after_filepath_in_twig_code_block: ~
     no_blank_line_after_filepath_in_xml_code_block: ~

.github/workflows/ci.yaml

@@ -73,7 +73,7 @@ jobs:
                     key: ${{ runner.os }}-doctor-rst-${{ steps.extract_base_branch.outputs.branch }}
 
             -   name: "Run DOCtor-RST"
-                uses: docker://oskarstark/doctor-rst:1.60.1
+                uses: docker://oskarstark/doctor-rst:1.61.1
                 with:
                     args: --short --error-format=github --cache-file=/github/workspace/.cache/doctor-rst.cache
 

components/property_access.rst

@@ -249,16 +249,21 @@ The ``getValue()`` method can also use the magic ``__get()`` method::
         {
             return $this->children[$id];
         }
+
+        public function __isset($id): bool
+        {
+            return true;
+        }
     }
 
     $person = new Person();
 
     var_dump($propertyAccessor->getValue($person, 'Wouter')); // [...]
 
-.. note::
+.. caution::
 
-    The ``__get()`` method support is enabled by default.
-    See `Enable other Features`_ if you want to disable it.
+    When implementing the magic ``__get()`` method, you also need to implement
+    ``__isset()``.
 
 .. _components-property-access-magic-call:
 

event_dispatcher.rst

@@ -162,7 +162,10 @@ having to add any configuration in external files::
         }
     }
 
-You can add multiple ``#[AsEventListener]`` attributes to configure different methods::
+You can add multiple ``#[AsEventListener]`` attributes to configure different methods.
+The ``method`` property is optional, and when not defined, it defaults to
+``on`` + uppercased event name. In the example below, the ``'foo'`` event listener
+doesn't explicitly define its method, so the ``onFoo()`` method will be called::
 
     namespace App\EventListener;
 

frontend/asset_mapper.rst

@@ -623,9 +623,7 @@ which will automatically do most of these things for you:
 - **Compress your assets**: Your web server should compress (e.g. using gzip)
   your assets (JavaScript, CSS, images) before sending them to the browser. This
   is automatically enabled in Caddy and can be activated in Nginx and Apache.
-  In Cloudflare, assets are compressed by default and you can also
-  enable `auto minify`_ to further compress your assets (e.g. removing
-  whitespace and comments from JavaScript and CSS files).
+  In Cloudflare, assets are compressed by default.
 
 - **Set long-lived cache expiry**: Your web server should set a long-lived
   ``Cache-Control`` HTTP header on your assets. Because the AssetMapper component includes a version
@@ -694,8 +692,8 @@ Does the AssetMapper Component Minify Assets?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Nope! Minifying or compressing assets *is* important, but can be
-done by your web server or a service like Cloudflare. See
-:ref:`Optimization <optimization>` for more details.
+done by your web server. See :ref:`Optimization <optimization>` for
+more details.
 
 Is the AssetMapper Component Production Ready? Is it Performant?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -1116,7 +1114,6 @@ command as part of your CI to be warned anytime a new vulnerability is found.
 .. _class syntax: https://caniuse.com/es6-class
 .. _UX React Documentation: https://symfony.com/bundles/ux-react/current/index.html
 .. _UX Vue.js Documentation: https://symfony.com/bundles/ux-vue/current/index.html
-.. _auto minify: https://developers.cloudflare.com/support/speed/optimization-file-size/using-cloudflare-auto-minify/
 .. _Lighthouse: https://developers.google.com/web/tools/lighthouse
 .. _Tailwind: https://tailwindcss.com/
 .. _BabdevPagerfantaBundle: https://github.com/BabDev/PagerfantaBundle

http_cache/_expiration-and-validation.rst.inc

@@ -5,10 +5,3 @@
     both worlds. In other words, by using both expiration and validation, you
     can instruct the cache to serve the cached content, while checking back
     at some interval (the expiration) to verify that the content is still valid.
-
-    .. tip::
-
-        You can also define HTTP caching headers for expiration and validation by using
-        annotations. See the `FrameworkExtraBundle documentation`_.
-
-.. _`FrameworkExtraBundle documentation`: https://symfony.com/doc/current/bundles/SensioFrameworkExtraBundle/annotations/cache.html

notifier.rst

@@ -56,7 +56,7 @@ their priorities:
 
 This event is dispatched after the controller has been resolved but before executing
 it. It's useful to initialize things later needed by the
-controller, such as `param converters`_, and even to change the controller
+controller, such as `value resolvers`_, and even to change the controller
 entirely::
 
     use Symfony\Component\HttpKernel\Event\ControllerEvent;
@@ -297,4 +297,4 @@ their priorities:
 
     $ php bin/console debug:event-dispatcher kernel.exception
 
-.. _`param converters`: https://symfony.com/doc/master/bundles/SensioFrameworkExtraBundle/annotations/converters.html
+.. _`value resolvers`: https://symfony.com/doc/current/controller/value_resolver.html#managing-value-resolvers