kenaug74/Sylius
1
0
Fork 0
mirror of https://github.com/Sylius/Sylius.git synced 2026-07-05 20:57:12 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

[Maintenance] Add UPGRADE-2.3 note about named arguments in validation constraints

Browse source
This commit is contained in:
Grzegorz Sadowski 2026-06-18 09:52:08 +02:00
parent a167cac1db
commit 5897846cbd
No known key found for this signature in database
GPG key ID: EF87FF4E6E3BD364
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
UPGRADE-2.3.md
View file

@ -108,6 +108,22 @@
as `type="object"` (`PaymentSecurityToken.details` and `PaymentRequest.payload`), it registers
a custom `Sylius\Bundle\PaymentBundle\Doctrine\DBAL\Type\ObjectType` to keep them working.
## Validation
1. Passing an array of options to configure a Sylius validation constraint is **deprecated** since Sylius 2.3
and will be removed in Sylius 3.0. Use named arguments instead.
All Sylius validation constraints now declare explicit constructors with named arguments
(marked with `#[HasNamedArguments]`). The legacy array syntax keeps working, it only triggers deprecation.
Configuring constraints via **XML / YAML / PHP attributes is not affected** and requires no changes; the validator
loaders pass the options as named arguments automatically. Only **direct instantiation in PHP** should be migrated:
```diff
-new ProvinceAddressConstraint(['message' => 'My custom message'])
+new ProvinceAddressConstraint(message: 'My custom message')
```
## Deprecations
1. Passing a `Sylius\Component\Core\Calculator\ProductVariantPricesCalculatorInterface` directly to the following catalog-facing classes is deprecated since Sylius 2.3.