Introduce new events: $onDragCommitted
and $onDragTransformed
#749
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds two new drag end events:
$onDragCommitted
and$onDragTransformed
. These allow consumers to handle drag endings differently depending on whether the drag was committed to the DOM or just transformed.Both event payloads emit the following details:
The
$onDragCommitted
event is fired when a drag ends and changes are reconciled back to the data store. The$onDragTransformed
event is fired if there is no reconciliation, but the element is transformed visually.The motivation for this change is to allow consumers to handle committed drags differently than drags that were just transformed with no data changes. For example, triggering a re-render or data fetch on commit but not on transform.