- 🇪🇸Spain akalam
I think it was because the patch is for the 6.x branch and the pipeline was trying to apply it against the 5.x branch. I tried to re-test the patch against 6.x, it applies but now a test is failing
Assume you are doing a migration where first images are imported and later you want to wrap those images into media entities.
The last stage would look like this:
field_image/target_id:
-
plugin: migration_lookup
migration: d7_image_migration
source: 'field_image/0/fid'
-
plugin: skip_on_empty
method: process
-
plugin: entity_generate
value_key: field_media_image/target_id
entity_type: media
bundle_key: bundle
bundle: image
values:
field_media_image/width: field_image/0/width
field_media_image/height: field_image/0/height
field_media_image/title: field_image/0/title
field_media_image/alt: field_image/0/alt
The issue here is with the lookup key defined behind value_key as it does not allow to use separators right now and in order to even make it work one can only use the field name without the property (target_id), but in this case when the further properties under values are added they will override the target id as it wasn't nested.
Support the row property separator and properly explode it and set nested properties in EntityLookup and EntityGenerate.
Needs work
6.0
API
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I think it was because the patch is for the 6.x branch and the pipeline was trying to apply it against the 5.x branch. I tried to re-test the patch against 6.x, it applies but now a test is failing