You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CheckSerializerCompilerPass: do not fail the container compilation when the serializer is disabled #278
CheckSerializerCompilerPass (added for #74) makes the container compilation fail when the Symfony serializer is not enabled. Only 6 services need it: NormalizerTask, DenormalizerTask, SerializerTask, DeserializerTask, NormalizeTransformer, DenormalizeTransformer. An application that does not use them still has to enable framework.serializer.
The same question applies to ValidatorTask and framework.validation.
Proposed fix
When no serializer is available, remove the serializer-dependent services (or replace them by a definition throwing the current explicit message when the task/transformer is used), instead of failing at compile time.
Same treatment for ValidatorTask if it has the same issue.
Drop the compiler pass (or deprecate it, it is a public class).
Note: this relaxes a constraint (the container compiles in more cases), it could also land in a v5 minor version.
Requirements
Documentation updates
Reference
Cookbooks
Changelog
Unit tests
Breaking changes
None for applications (the error moves from the container compilation to the process execution). CheckSerializerCompilerPass is removed (minor: internal class, unlikely to be used outside the bundle).
Activity
Merge pull request #289 from cleverage/278
njoubert-cleverage commentedon Oct 14, 2026
Fixed by #289 (merged, 47b2990).