Problem/Motivation
We added \Drupal\dynamic_entity_reference\Normalizer\DynamicEntityReferenceItemNormalizer for hal in #2332117: Add a DynamicEntityReferenceItemNormalizer. We also need one for serialization module.
Proposed resolution
Add DynamicEntityReferenceItemNormalizer for serialization module
Remaining tasks
Create a patch wait #2827164: Entity reference field normalization has target_type and target_uuid, but not used in denormalization to get fixed.
User interface changes
None
API changes
DER will support plain json serialization.
Data model changes
None.
Comments
Comment #2
wim leers#2827164: Entity reference field normalization has target_type and target_uuid, but not used in denormalization finally landed! This issue can now continue :)
Comment #3
wim leers#2970836: Argument 3 passed to Drupal\hal\Normalizer\EntityReferenceItemNormalizer::__construct() must implement interface Drupal\Core\Entity\EntityTypeManagerInterface or be null happened, and made the normalizer specifically conditionally only load for
hal. I guess this is a low priority. Understandably so of course!Comment #4
a-fro commentedI'm running into issues with a project that's using Tome for static site generation. When calling
drush tome:installeverything works fine importing the content until it tries to generate serialized entities that are using dynamic entity reference. The error that gets thrown isI'll probably create an issue on the Tome project as well, but I think this might be related to the missing serialization normalizer for DER. Does that sound right? Any chance I could help pitch in to create the patch on this issue if so?
Comment #5
larowlanYes, this issue would need to be resolved. Please close the tome issue.