Support Entity Clone

I guess as a solution we can use a custom clone callback:

  /**
   * {@inheritdoc}
   */
  public function cloneEntity(EntityInterface $entity, EntityInterface $cloned_entity, array $properties = [], array &$already_cloned = []) {
    $cloned_entity = parent::cloneEntity($entity, $cloned_entity);

    $registration_storage = \Drupal::entityTypeManager()->getStorage('registration_settings');

    $registration_query = $registration_storage->getQuery();
    $registration_query->accessCheck(FALSE);
    $registration_query->condition('entity_type_id', $entity->getEntityTypeId());
    $registration_query->condition('entity_id', $entity->id());

    if ($results = $registration_query->execute()) {
      $registration_id = reset($results);
      $registration = $registration_storage->load($registration_id);

      $duplicate = $registration->createDuplicate();
      $duplicate->set('entity_id', $cloned_entity->id());
      $duplicate->save();
    }

    return $cloned_entity;
  }

@Aston, yes, Overall, this code ensures that when an entity is cloned, any associated registration settings are also cloned and associated with the new entity. This allows for consistent behavior when cloning entities with registration settings

yeah,
but my question: is it possible to do it without writing custom code? e.g. a new submodule

@Aston, I think depending on the specific requirements and intricacies of your use case, you may still need to implement custom code or configuration to achieve the desired outcome.

Unfortunately the approach here is blocked by an upstream issue ✨ Add PRE_CLONE/POST_CLONE event dispatch handling to sub referenced entities Needs work . So we should postpone this on that.

john.oltman → closed merge request !38