-
-
Notifications
You must be signed in to change notification settings - Fork 960
refactor: split normalizer/denormalizer #7713
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
soyuka
commented
Jan 28, 2026
| Q | A |
|---|---|
| Branch? | main |
| Tickets | prerequisite for #7710 |
| License | MIT |
| Doc PR | na |
a551716 to
ea40daf
Compare
| * @author Amrouche Hamza <hamza.simperfit@gmail.com> | ||
| * @author Baptiste Meyer <baptiste.meyer@gmail.com> | ||
| * | ||
| * @todo Denormalization methods should be deprecated in 5.x, use ItemDenormalizer instead |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should ItemNormalizer::denormalize call ItemDenormalizer::denormalize to ensure that futur bugfix/feature will be done on both ?
Cause we're having duplicate code with denormalize no ?
| public const FORMAT = 'jsonapi'; | ||
|
|
||
| private array $componentsCache = []; | ||
| use ItemNormalizerTrait; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there some methods to remove here ?
Like supportsDenormalization which is already in the trait if I read correctly
| * | ||
| * @throws NotNormalizableValueException | ||
| * | ||
| * @todo This method should be deprecated in 5.x, use ItemDenormalizer instead |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same, could it call ItemDenormalizer::denormalize ?