Update UniqueIdentifier interface to allow number ids #755
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.
The
UniqueIdentifier
type has been updated to now accept eitherstring
ornumber
identifiers. As a result, theid
property ofuseDraggable
,useDroppable
anduseSortable
and theitems
prop of<SortableContext>
now all accept eitherstring
ornumber
identifiers.Migration steps
For consumers that are using TypeScript, import the
UniqueIdentifier
type to have strongly typed local state:Alternatively, consumers can cast or convert the
id
property to astring
when reading theid
property of interfaces such asActive
,Over
,DroppableContainer
andDraggableNode
.The
draggableNodes
object has also been converted to a map. Consumers that were reading from thedraggableNodes
property that is available on the public context of<DndContext>
should follow these migration steps: