From 1e186fab58d19743f13345c85d842189e66a8742 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Julien=20Fastr=C3=A9?= Date: Wed, 29 Oct 2025 12:26:46 +0100 Subject: [PATCH] Document validation update guidelines for `ThirdParty` entity to align with associated Vue component logic. - Added documentation to ensure updates in validations reflect in `ThirdPartyEdit.vue` and violation lists for consistency. - Clarified the relationship between validation logic and UI component updates. --- src/Bundle/ChillThirdPartyBundle/Entity/ThirdParty.php | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/Bundle/ChillThirdPartyBundle/Entity/ThirdParty.php b/src/Bundle/ChillThirdPartyBundle/Entity/ThirdParty.php index d79ff5cc0..480e67cfc 100644 --- a/src/Bundle/ChillThirdPartyBundle/Entity/ThirdParty.php +++ b/src/Bundle/ChillThirdPartyBundle/Entity/ThirdParty.php @@ -69,6 +69,11 @@ use Symfony\Component\Validator\Constraints as Assert; * * The difference between categories and types is transparent for user: they choose the same fields into the UI, without * noticing a difference. + * + * ## Validation + * + * When a validation is inserted / updated, do not forget to update the related ThirdPartyEdit.vue component and the associated + * list of possible violations. */ #[ORM\Entity] #[ORM\Table(name: 'chill_3party.third_party')]