[PropertyInfo] Added an versionadded block to explicitly denote what behavior has changed with symfony 6.4

jbtronics · jbtronics · commit d759f8db5505 · 2023-09-30T20:55:16.000+02:00
diff --git a/components/property_info.rst b/components/property_info.rst
@@ -225,9 +225,15 @@ provide whether properties are readable or writable as booleans::
 The :class:`Symfony\\Component\\PropertyInfo\\Extractor\\ReflectionExtractor` looks
 for getter/isser/setter/hasser method in addition to whether or not a property is public
 to determine if it's accessible. This based on how the :doc:`PropertyAccess </components/property_access>`
-works. It assumes camel-case style method names following `PSR-1`_. Therefore, a property like ``myProperty`` or ``my_property`` is
+works. It assumes camel case style method names following `PSR-1`_. Therefore, a property like ``myProperty`` or ``my_property`` is
 readable if it has a ``getMyProperty()`` and writable if it has a ``setMyProperty()`` method.
 
+.. versionadded:: 6.4
+
+    Camel case style setter methods for properties in snake case (like ``my_property``) are accepted since Symfony 6.4. Before, the
+    setter name had to contain the underscores (e.g. `setMy_property()`) to make the property assumed writable.
+
+
 .. _property-info-initializable:
 
 Property Initializable Information
