Would be great if, comparable to edit-form and delete-form, an entity could declare a duplicate-form link, and receive a route, local task, form, etc.
Core has a problem in this area worth solving, it is not possible to react to an entity being duplicated. Only the regular save hooks are fired, which give no info on what the original entity was. It would be great if we could figure out a workaround for that as well, so that we can respond to the duplication. For example, when duplicating a bundle entity it is desirable to clone the attached fields and displays.
The cleanest way would probably be to invoke a hook_entity_duplicate() from a trait that can be used form any entity form.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | 3023884-6.patch | 47.36 KB | bojanz |
| #5 | 3023884-5.patch | 39.33 KB | bojanz |
| #4 | 3023884-4-entity-duplicate.patch | 32.37 KB | bojanz |
Comments
Comment #2
bojanz commentedAdding core issue for the related problem.
Comment #3
hchonovI think that we need some form of cascade - for example in the case of nested entity structures, where the referenced entities "might" need to be duplicated as well.
The best would be if we could automate the process without the need to implement any hooks manually - for example if we could find out which referenced entities or dependencies are unique to the current entity and duplicate them as well.
Comment #4
bojanz commentedWIP.
Adds an explicit "duplicate" access operation with matching permissions. Felt cleaner than abusing create/update.
Comment #5
bojanz commentedThis should be the final patch.
Cleaned up the EntityDuplicateTrait a bit. Added an automatic "Duplicate" operation. Added a test.
Comment #6
bojanz commentedFixed test.
Fixed the permission logic to only provide duplicate permissions if there is a duplicate form, which is cleaner.
Comment #8
bojanz commentedCommitted #6.
Followup: #3041219: Add a helper for duplicating bundle entities, invoke it when needed.