chore(deps): bump @dnd-kit/core from 6.0.7 to 6.3.1

[dependabot]

Bumps @dnd-kit/core from 6.0.7 to 6.3.1.

Release notes

Sourced from @​dnd-kit/core's releases.

@​dnd-kit/core@​6.3.1

Patch Changes

• #1555 62f632a Thanks @​clauderic! - Added Tab to the list of default key codes that end a drag and drop operation. Can be customized by passing in a custom list of keyCodes to the KeyboardSensor options.

@​dnd-kit/core@​6.3.0

Minor Changes

• #1539 0c6a28d Thanks @​irobot! - Make it possible to add visual cues when using activation constraints.

  Context

  Activation constraints are used when we want to prevent accidental dragging or when pointer press can mean more than "start dragging".

  A typical use case is a button that needs to respond to both "click" and "drag" gestures. Clicks can be distinguished from drags based on how long the pointer was held pressed.

  The problem

  A control that responds differently to a pointer press based on duration or distance can be confusing to use -- the user has to guess how long to keep holding or how far to keep dragging until their intent is acknowledged.

  Implementing such cues is currently possible by attaching extra event listeners so that we know when a drag is pending. Furthermore, the listener needs to have access to the same constraints that were applied to the sensor initiating the drag. This can be made to work in simple cases, but it becomes error-prone and difficult to maintain in complex scenarios.

  Solution

  This changeset proposes the addition of two new events: onDragPending and onDragAbort.

  onDragPending

  A drag is considered to be pending when the pointer has been pressed and there are activation constraints that need to be satisfied before a drag can start.

  This event is initially fired on pointer press. At this time offset (see below) will be undefined.

  It will subsequently be fired every time the pointer is moved. This is to enable visual cues for distance-based activation.

  The event's payload contains all the information necessary for providing visual feedback:

  export interface DragPendingEvent {

... (truncated)

Changelog

Sourced from @​dnd-kit/core's changelog.

6.3.1

Patch Changes

• #1555 62f632a Thanks @​clauderic! - Added Tab to the list of default key codes that end a drag and drop operation. Can be customized by passing in a custom list of keyCodes to the KeyboardSensor options.

6.3.0

Minor Changes

• #1539 0c6a28d Thanks @​irobot! - Make it possible to add visual cues when using activation constraints.

  Context

  Activation constraints are used when we want to prevent accidental dragging or when pointer press can mean more than "start dragging".

  A typical use case is a button that needs to respond to both "click" and "drag" gestures. Clicks can be distinguished from drags based on how long the pointer was held pressed.

  The problem

  A control that responds differently to a pointer press based on duration or distance can be confusing to use -- the user has to guess how long to keep holding or how far to keep dragging until their intent is acknowledged.

  Implementing such cues is currently possible by attaching extra event listeners so that we know when a drag is pending. Furthermore, the listener needs to have access to the same constraints that were applied to the sensor initiating the drag. This can be made to work in simple cases, but it becomes error-prone and difficult to maintain in complex scenarios.

  Solution

  This changeset proposes the addition of two new events: onDragPending and onDragAbort.

  onDragPending

  A drag is considered to be pending when the pointer has been pressed and there are activation constraints that need to be satisfied before a drag can start.

  This event is initially fired on pointer press. At this time offset (see below) will be undefined.

  It will subsequently be fired every time the pointer is moved. This is to enable visual cues for distance-based activation.

  The event's payload contains all the information necessary for providing visual feedback:

... (truncated)

Commits

• 97c1609 Version Packages
• 62f632a End keyboard drag operation when pressing tab
• 060c982 Version Packages
• 9175566 Merge branch 'master' into feature/constraint-cues
• 2eedcc3 Version Packages
• 835ae76 Lint
• 3c4f627 Merge pull request #1543 from clauderic/patch-1
• baad391 Merge pull request #1542 from clauderic/fix-zero-id
• b7f46bb Merge pull request #1541 from clauderic/handle-cancel-events
• 2eb636f Merge pull request #1435 from knaveenkumar3576/user/knaveenkumar3576/improved...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)