`onbeforedelete` should give back `event` about xyflow HOT 2 OPEN

@mcmxcdev You can just return true inside the onbeforedelete handler so the elements get deleted (false if deletion has not been confirmed). There is no need to actually programmatically delete the elements.

However, I still see you point. I assume there might be a reason to delete those elements programmatically, or to simply distinguish what has triggered the deletion (user input vs. program).

What do you think about an optional force parameter for deleteElements that skips onbeforedelete?

from xyflow.

It's not that we trigger an async request in onbeforedelete that needs to be awaited until it can be deleted. It's a modal window that might or might not confirm the deletion. So we are taken completely out of the flow of onbeforedelete, hence we need programatical deletion.

However, I still see you point. I assume there might be a reason to delete those elements programmatically, or to simply distinguish what has triggered the deletion (user input vs. program).

Yes, 100%

What do you think about an optional force parameter for deleteElements that skips onbeforedelete?

That would sound reasonable to fix the issue I am experiencing, but other users might run into situations where they would need event exposed for other use cases, so I would still consider that important.

from xyflow.