From 395837a11a7a05a9598a56ed70d263d1357bb83c Mon Sep 17 00:00:00 2001 From: mscherer Date: Fri, 17 Oct 2025 16:27:27 +0200 Subject: [PATCH] Document allowNullableNull change. --- en/appendices/5-3-migration-guide.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/en/appendices/5-3-migration-guide.rst b/en/appendices/5-3-migration-guide.rst index e4d393f24a..8b41df47a7 100644 --- a/en/appendices/5-3-migration-guide.rst +++ b/en/appendices/5-3-migration-guide.rst @@ -27,6 +27,10 @@ Validation - The signature of ``Validator::validate(array $data, bool $newRecord = true, array $context = [])`` has now a additional third parameter ``$context``. It can be used to pass necessary context into the validation when marshalling. +- The ``existsIn`` validation rule now defaults ``allowNullableNulls`` to ``true`` instead of ``false``. + This means that ``null`` values in nullable foreign keys will pass validation by default, which is more + semantically correct for optional relationships. If you need the previous behavior where ``null`` values + fail validation, you can explicitly set ``allowNullableNulls`` to ``false`` in your validation rules. View ----