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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@dnd-kit/core@1.2.0
Minor Changes
79f6088
#144 Thanks @clauderic! - Allow consumers to determine whether to animate layout changes and when to measure nodes. Consumers can now use theanimateLayoutChanges
prop ofuseSortable
to determine whether layout animations should occur. Consumers can now also decide when to measure layouts, and at what frequency using thelayoutMeasuring
prop ofDndContext
. By default,DndContext
will measure layouts just-in-time after sorting has begun. Consumers can override this behaviour to either only measure before dragging begins (on mount and after dragging), or always (on mount, before dragging, after dragging). Pairing thelayoutMeasuring
prop onDndContext
and theanimateLayoutChanges
prop ofuseSortable
opens up a number of new possibilities for consumers, such as animating insertion and removal of items in a sortable list.a76cd5a
#136 Thanks @clauderic! - AddedonActivation
option to sensors. Delegated the responsibility of callingevent.preventDefault()
on activation to consumers, as consumers have the most context to decide whether it is appropriate or not to prevent the default browser behaviour on activation. Consumers of the sensors can prevent the default behaviour on activation using theonActivation
option. Here is an example using the Pointer sensor:useSensor(PointerSensor, {onActivation: (event) => event.preventDefault()})
Patch Changes
adb7bd5
#151 Thanks @clauderic! -DragOverlay
now attempts to perform drop animation even iftransform.x
andtransform.y
are both zero.@dnd-kit/sortable@1.1.0
Minor Changes
79f6088
#144 Thanks @clauderic! - Allow consumers to determine whether to animate layout changes and when to measure nodes. Consumers can now use theanimateLayoutChanges
prop ofuseSortable
to determine whether layout animations should occur. Consumers can now also decide when to measure layouts, and at what frequency using thelayoutMeasuring
prop ofDndContext
. By default,DndContext
will measure layouts just-in-time after sorting has begun. Consumers can override this behaviour to either only measure before dragging begins (on mount and after dragging), or always (on mount, before dragging, after dragging). Pairing thelayoutMeasuring
prop onDndContext
and theanimateLayoutChanges
prop ofuseSortable
opens up a number of new possibilities for consumers, such as animating insertion and removal of items in a sortable list.Patch Changes
adb7bd5
,79f6088
,a76cd5a
]: