feat(): drop:before event

[ShaMan123]

No description provided.

[asturur]

wait, which is the difference between drop:before and drop at this point?
if you register more than one drop:before event you have the exact same issue that with the drop event.

I m not opposed to this at all, just i want to understand better.

[ShaMan123]

The idea is to use drop:before on objects, perform logic and decide if to block the canvas from handling the drop as well.
We can fire the drop event first on the target before firing canvas but it is out of norm as far as the other events

[ShaMan123]

For example

        obj.on('drop:before', (opt) => {
            let handled = false;
            // logic mutating `handled`
            handled && opt.e.preventDefault();
        })

        canvas.on('drop', (opt) => {
            if (opt.e.defaultPrevented) return;
            //  handle the drop
        })

[ShaMan123]

Another use case would be handling drop on objects in a different order than object stack order

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[asturur]

Sorry i m late on this.
Ok i m not super into this, but is not bad.
I will change the comment and merge it.

[asturur]

that object you set the drop:before event on, could be the object that is in the target of the normal drop event.
I understand that sometimes we don't want to have big even thandlers that take care of everything in a single function.