Allow for more robust duplication actions

[xaviemirmon]

          @chrisvxd  do we have any updates on this one ? 

Also is there any way to capture the duplicateEvent? The issue i'm facing is while duplicating the component it creating copy with same id value for it and hence when trying to update my db, it throws error as there is primary key constraint on the id column. I need some way to control this duplicate action.

Originally posted by @sagarchoudhary96 in #461 (comment)

[xaviemirmon]

In #461, @sagarchoudhary96 mentions the requirement for better handling/access to the duplication action.

I ran into problems similar to those in my implementation, which is leveraging additional metadata behind the scenes. Rather than exposing the entire Dropzone context and dispatch function, perhaps we can update the duplicate action to add a flag to the duplicated and change the ID such as isDuplicate={true}?

Then, when using the onPublish, we could alter the data/behaviour before sending the payload to the server. Are there any reasons we shouldn't just do this?

const newItem = {
  ...item,
  props: {
    ...item.props,
    id: generateId(item.type),
    // Track if the item is a duplicate
    isDuplicate: true
  },
};

@sagarchoudhary96 I am confused by the output you've provided in your screenshot. id is a string of {type}-{uuid} in the props object, not the main component object. Are you setting that value yourself somehow?

[xaviemirmon]

Related to #538

I think the new onAction could solve some of these problems too!