No, I don't think so. module_edit is for a particular module within a unit. All we would be doing is passing a function to module_edit, and all the logic of how the operation is done would still be within unit.coffee (since it needs the parent location and needs to insert the new component into the new place).

I originally coded it that way (following the same sort of pattern as the onDelete callback which is passed to module_edit), but it just didn't feel like it made sense. It also forced me to add code into the tabs.coffee file, even though tabs will not support duplicate.