Drupal
/
drupal
mirror of https://git.drupalcode.org/project/drupal.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Issue #3479185 by akulsaxena, joachim, smustgrave, mikelutz, quietone: Clarify documentation for EntityContentBase 'translations' configuration option

merge-requests/7809/merge
quietone 2024-12-19 21:53:45 +13:00
parent 2e2f1d7786
commit edf709a383
No known key found for this signature in database
GPG Key ID: 43BFBBB26EA09FE1
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
core/modules/migrate/src/Plugin/migrate/destination/EntityContentBase.php
View File

@ -27,8 +27,14 @@ use Symfony\Component\DependencyInjection\ContainerInterface;
* Provides destination class for all content entities lacking a specific class.
*
* Available configuration keys:
* - translations: (optional) Boolean, indicates if the entity is translatable,
* defaults to FALSE.
* - translations: (optional) A boolean that indicates if the entity is
* translatable. When TRUE, migration rows will be considered as translations.
* This means the migration will attempt to load an existing entity and, if
* found, save the row data into it as a new translation rather than creating
* a new entity. For this functionality, the migration process definition must
* include mappings for the entity ID and the entity language field. If this
* property is TRUE, the migration will also have an additional destination ID
* for the language code.
* - overwrite_properties: (optional) A list of properties that will be
* overwritten if an entity with the same ID already exists. Any properties
* that are not listed will not be overwritten.