[ERP-45] Implémenter Provider et Processor Category #17
Reference in New Issue
Block a user
Delete Branch "feature/ERP-45-implementer-provider-processor-category"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Mode stacked PR — cible
feature/ERP-44-creer-entites-categoryRésumé
CategoryProvider: filtre soft-delete par défaut (RG-1.08),?includeDeleted=true(RG-1.09), tri name ASC (RG-1.10), 404 si soft-deleted hors flag (RG-1.11).CategoryProcessor: trim duname(RG-1.03), conversion DELETE → UPDATE (RG-1.12), mappingUniqueConstraintViolationException→ HTTP 409 avec message exact (RG-1.07).#[ApiResource]deCategory. Provider câblé aussi sur Patch + Delete (au-delà du scope strict du ticket) pour fermer la fuite RG-1.11 sur PATCH.DoctrineCategoryRepositoryexposecreateListQueryBuilder($includeDeleted).Décisions notables
adu ticket) : pas de filtre Doctrine global, lisibilité directe.remove_processorinjecté : la DELETE est convertie en UPDATE via lepersist_processor. API Platform 4 utilise le processor déclaré sur l'opération sans fallback automatique.Category.php.Tests
make php-cs-fixer-allow-risky✓make test✓ (248 tests, 0 régression — pas de test métier Category, c'est ERP-48)Tickets
docs/specs/M0-categories/spec-back.md§ 4.1 + § 4.3 + § 4.4 + § 4.5Suite
ae70e90db2to0607ad8676