Skip to content

Commit 734508f

Browse files
committed
Merge branch '7.4' into 8.0
* 7.4: Make public property requirement clearer for constraint options [Lock] Add support for keys serialization using the Serializer component
2 parents 0c0dbc6 + 5c22c52 commit 734508f

File tree

2 files changed

+10
-1
lines changed

2 files changed

+10
-1
lines changed

components/lock.rst

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,15 @@ example, the kernel will automatically release semaphores acquired by the
128128
store (see :ref:`lock stores <lock-stores>` for supported stores), an
129129
exception will be thrown when the application tries to serialize the key.
130130

131+
Locks can be serialized using both the native PHP serialization system
132+
and its :phpfunction:`serialize` function, or using the Serializer
133+
component.
134+
135+
.. versionadded:: 7.4
136+
137+
The support for serializing locks with the Serializer component was
138+
introduced in Symfony 7.4.
139+
131140
.. _lock-blocking-locks:
132141

133142
Blocking Locks

validation/custom_constraint.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -259,7 +259,7 @@ You can use custom validators like the ones provided by Symfony itself:
259259
}
260260
}
261261
262-
If your constraint contains options, then they should be public properties
262+
If your constraint contains options, then they must be public properties
263263
on the custom Constraint class you created earlier. These options can be
264264
configured like options on core Symfony constraints.
265265

0 commit comments

Comments
 (0)