Bump @dnd-kit/sortable from 5.1.0 to 8.0.0

[dependabot]

Bumps @dnd-kit/sortable from 5.1.0 to 8.0.0.

Release notes

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

@​dnd-kit/sortable@​8.0.0

Patch Changes

• Updated dependencies [bc588c7, b417f0f, f342d5e]:
  • @​dnd-kit/core@​6.1.0
  • @​dnd-kit/utilities@​3.2.2

@​dnd-kit/sortable@​7.0.2

Patch Changes

• #788 da94c02 Thanks @​clauderic! - Bug fixes for React 18 Strict Mode

• Updated dependencies [da94c02]:

  • @​dnd-kit/core@​6.0.7

@​dnd-kit/sortable@​7.0.1

Patch Changes

• #792 b6970e7 Thanks @​clauderic! - The hasSortableData type-guard that is exported by @​dnd-kit/sortable has been updated to also accept the Active and Over interfaces so it can be used in events such as onDragStart, onDragOver, and onDragEnd.

• Updated dependencies [eaa6e12]:

  • @​dnd-kit/core@​6.0.4

@​dnd-kit/sortable@​7.0.0

Major Changes

• #755 33e6dd2 Thanks @​clauderic! - The UniqueIdentifier type has been updated to now accept either string or number identifiers. As a result, the id property of useDraggable, useDroppable and useSortable and the items prop of <SortableContext> now all accept either string or number identifiers.

  Migration steps

  For consumers that are using TypeScript, import the UniqueIdentifier type to have strongly typed local state:

  + import type {UniqueIdentifier} from '@dnd-kit/core';
  function MyComponent() {
  
  const [items, setItems] = useState(['A', 'B', 'C']);
  
  
  const [items, setItems] = useState<UniqueIdentifier>(['A', 'B', 'C']);
  }

Alternatively, consumers can cast or convert the id property to a string when reading the id property of interfaces such as Active, Over, DroppableContainer and DraggableNode.

The draggableNodes object has also been converted to a map. Consumers that were reading from the draggableNodes property that is available on the public context of <DndContext> should follow these migration steps:

- draggableNodes[someId];
+ draggableNodes.get(someId);

... (truncated)

Changelog

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

8.0.0

Patch Changes

• Updated dependencies [bc588c7, b417f0f, f342d5e]:
  • @​dnd-kit/core@​6.1.0
  • @​dnd-kit/utilities@​3.2.2

7.0.2

Patch Changes

• #788 da94c02 Thanks @​clauderic! - Bug fixes for React 18 Strict Mode

• Updated dependencies [da94c02]:

  • @​dnd-kit/core@​6.0.7

7.0.1

Patch Changes

• #792 b6970e7 Thanks @​clauderic! - The hasSortableData type-guard that is exported by @​dnd-kit/sortable has been updated to also accept the Active and Over interfaces so it can be used in events such as onDragStart, onDragOver, and onDragEnd.

• Updated dependencies [eaa6e12]:

  • @​dnd-kit/core@​6.0.4

7.0.0

Major Changes

• #755 33e6dd2 Thanks @​clauderic! - The UniqueIdentifier type has been updated to now accept either string or number identifiers. As a result, the id property of useDraggable, useDroppable and useSortable and the items prop of <SortableContext> now all accept either string or number identifiers.

  Migration steps

  For consumers that are using TypeScript, import the UniqueIdentifier type to have strongly typed local state:

  + import type {UniqueIdentifier} from '@dnd-kit/core';
  function MyComponent() {
  
  const [items, setItems] = useState(['A', 'B', 'C']);
  
  
  const [items, setItems] = useState<UniqueIdentifier>(['A', 'B', 'C']);
  }

Alternatively, consumers can cast or convert the id property to a string when reading the id property of interfaces such as Active, Over, DroppableContainer and DraggableNode.

The draggableNodes object has also been converted to a map. Consumers that were reading from the draggableNodes property that is available on the public context of <DndContext> should follow these migration steps:

... (truncated)

Commits

• 694dcc2 Version Packages (#1240)
• 880190f Version Packages (#986)
• da94c02 React 18 \<StrictMode> tweaks and bug fixes (#788)
• 8d1d0e8 Version Packages
• b6970e7 Add Active and Over in hasSortableData type guard
• d5838e6 Version Packages
• 33e6dd2 Update UniqueIdentifier interface to allow number ids (#755)
• e6d544f Fix a regression with layout animations (#757)
• 224201a Introduce disabled prop on SortableContext
• 5811986 Improve default sortableKeyboardCoordinates getter
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.