useDraggable

Arguments
1
interface UseDraggableArguments {
2
  id: string | number;
3
  attributes?: {
4
    role?: string;
5
    roleDescription?: string;
6
    tabIndex?: number;
7
  },
8
  data?: Record<string, any>;
9
  disabled?: boolean;
10
}
Copied!
Identifier
The id argument is a string or number that should be a unique identifier, meaning there should be no other draggable elements that share that same identifier within a given DndContext provider.
If you're building a component that uses both the useDraggable and useDroppable hooks, they can both share the same identifier since draggable elements are stored in a different key-value store than droppable elements.
Data
The data argument is for advanced use-cases where you may need access to additional data about the draggable element in event handlers, modifiers or custom sensors.
For example, if you were building a sortable preset, you could use the data attribute to store the index of the draggable element within a sortable list to access it within a custom sensor.
1
const {setNodeRef} = useDraggable({
2
  id: props.id,
3
  data: {
4
    index: props.index,
5
  },
6
});
Copied!
Another more advanced example where the data argument can be useful is create relationships between draggable nodes and droppable areas, for example, to specify which types of droppable nodes your draggable node can be dropped on:
1
import {DndContext, useDraggable, useDroppable} from '@dnd-kit/core';
2
​
3
function Droppable() {
4
  const {setNodeRef} = useDroppable({
5
    id: 'droppable',
6
    data: {
7
      type: 'type1',
8
    },
9
  });
10
​
11
  /* ... */
12
}
13
​
14
function Draggable() {
15
  const {attributes, listeners, setNodeRef, transform} = useDraggable({
16
    id: 'draggable',
17
    data: {
18
      supports: ['type1', 'type2'],
19
    },
20
  });
21
​
22
  /* ... */
23
}
24
​
25
function App() {
26
  return (
27
    <DndContext onDragEnd={handleDragEnd}>
28
      /* ... */
29
    </DndContext>
30
  );
31
  
32
  function handleDragEnd(event) {
33
    const {active, over} = event;
34
​
35
    if (over && active.data.current.supports.includes(over.data.current.type)) {
36
      // do stuff
37
    }
38
  }
39
}
Copied!
Disabled
Since hooks cannot be conditionally invoked, use the disabled argument and set it to true if you need to temporarily disable a draggable element.
Attributes
The default values for the attributes property are sensible defaults that should cover a wide range of use cases, but there is no one-size-fits-all solution.
You know your application best, and we encourage you to manually attach only the attributes that you think make sense in the context of your application rather than using them all without considering whether it makes sense to do so. 
For example, if the HTML element you are attaching the useDraggable listeners to is already a native HTML button element, although it's harmless to do so, there's no need to add the role="button" attribute, since that is already the default role of button. 
Role
The ARIA "role" attribute lets you explicitly define the role for an element, which communicates its purpose to assistive technologies.
The default value for the "role" attribute is "button". 
If it makes sense in the context of what you are building, we recommend that you leverage the native HTML <button> element for draggable elements.
Role description
The roleDescription argument can be used to tailor the screen reader experience to your application. For example, if you're building a sortable list of products you'd want to set the roleDescription value to something like "sortable product".
Tab index
The tabindex attribute dictates the order in which focus moves throughout the document.
Natively interactive elements such as buttons, anchor tags and form controls have a default tabindex value of 0. 
Custom elements that are intended to be interactive and receive keyboard focus need to have an explicitly assigned tabindex="0"(for example, div and li elements)
In other words, in order for your draggable elements to receive keyboard focus, they need to have the tabindex attribute set to 0 if they are not natively interactive elements (such as the HTML button element).
For this reason, the useDraggable hook sets the tabindex="0" attribute by default.
Properties
1
{
2
  active: {
3
    id: UniqueIdentifier;
4
    node: React.MutableRefObject<HTMLElement>;
5
    rect: ViewRect;
6
  } | null;
7
  attributes: {
8
    role: string;
9
    tabIndex: number;
10
    'aria-diabled': boolean;
11
    'aria-roledescription': string;
12
    'aria-describedby': string;
13
  },
14
  isDragging: boolean;
15
  listeners: Record<SyntheticListenerName, Function> | undefined;
16
  node: React.MutableRefObject<HTMLElement | null>;
17
  over: {id: UniqueIdentifier} | null;
18
  setNodeRef(HTMLElement | null): void;
19
  setActivatorNodeRef(HTMLElement | null): void;
20
  transform: {x: number, y: number, scaleX: number, scaleY: number} | null;
21
}
Copied!
Active
active
If there is currently an active draggable element within the DndContext provider where the useDraggable hook is used, the active property will be defined with the corresponding id, node and rect of that draggable element. 
Otherwise, the active property will be set to null.
isDragging
If the draggable element that is currently being dragged is the current one where useDraggable is used, the isDragging property will be true. Otherwise the isDragging property will be false.
Internally, the isActive property just checks if the active.id === id.
Listeners
The useDraggable hook requires that you attach listeners to the DOM node that you would like to become the activator to start dragging. 
While we could have attached these listeners manually to the node  provided to setNodeRef, there are actually a number of key advantages to forcing the consumer to manually attach the listeners.
Flexibility
While many drag and drop libraries need to expose the concept of "drag handles", creating a drag handle with the useDraggable hook is as simple as manually attaching the listeners to a different DOM element than the one that is set as the draggable source DOM node:
1
import {useDraggable} from '@dnd-kit/core';
2
​
3
​
4
function Draggable() {
5
  const {attributes, listeners, setNodeRef} = useDraggable({
6
    id: 'unique-id',
7
  });
8
  
9
  return (
10
    <div ref={setNodeRef}>
11
      /* Some other content that does not activate dragging */
12
      <button {...listeners} {...attributes}>Drag handle</button>
13
    </div>
14
  );
15
}
Copied!
When attaching the listeners to a different element than the node that is draggable, make sure you also attach the attributes to the same node that has the listeners attached so that it is still accessible. 
You can even have multiple drag handles if that makes sense in the context of your application:
1
import {useDraggable} from '@dnd-kit/core';
2
​
3
​
4
function Draggable() {
5
  const {attributes, listeners, setNodeRef} = useDraggable({
6
    id: 'unique-id',
7
  });
8
  
9
  return (
10
    <div ref={setNodeRef}>
11
      <button {...listeners} {...attributes}>Drag handle 1</button>
12
      /* Some other content that does not activate dragging */
13
      <button {...listeners} {...attributes}>Drag handle 2</button>
14
    </div>
15
  );
16
}
Copied!
Performance
This strategy also means that we're able to use React synthetic events, which ultimately leads to improved performance over manually attaching event listeners to each individual node.

Why? Because rather than having to attach individual event listeners for each draggable DOM node, React attaches a single event listener for every type of event we listen to on the document. Once click on one of the draggable nodes happens, React's listener on the document dispatches a SyntheticEvent back to the original handler. 
Node
setNodeRef
In order for the useDraggable hook to function properly, it needs the setNodeRef property to be attached to the HTML element you intend on turning into a draggable element so that @dnd-kit can measure that element to compute collisions:
1
function Draggable(props) {
2
  const {setNodeRef} = useDraggable({
3
    id: props.id,
4
  });
5
  
6
  return (
7
    <button ref={setNodeRef}>
8
      {/* ... */}
9
    </button>
10
  );
11
}
Copied!
Keep in mind that the ref should be assigned to the outer container that you want to become draggable, but this doesn't necessarily need to coincide with the container that the listeners are attached to.
node
A ref to the current node that is passed to setNodeRef
Activator
setActivatorNodeRef
It's possible for the listeners to be attached to a different node than the one that setNodeRef is attached to.
A common example of this is when implementing a drag handle and attaching the listeners to the drag handle:
1
function Draggable(props) {
2
  const {listeners, setNodeRef} = useDraggable({
3
    id: props.id,
4
  });
5
  
6
  return (
7
    <div ref={setNodeRef}>
8
      {/* ... */}
9
      <button {...listeners}>Drag handle</button>
10
    </div>
11
  );
12
}
Copied!
When the activator node differs from the draggable node, we recommend setting the activator node ref on the activator node:
1
function Draggable(props) {
2
  const {listeners, setNodeRef, setActivatorNodeRef} = useDraggable({
3
    id: props.id,
4
  });
5
  
6
  return (
7
    <div ref={setNodeRef}>
8
      {/* ... */}
9
      <button ref={setActivatorNodeRef} {...listeners}>Drag handle</button>
10
    </div>
11
  );
12
}
Copied!
This helps @dnd-kit more accurately handle automatic focus management and can also be accessed by sensors for enhanced activation constraints.
Focus management is automatically handled by @dnd-kit. When the activator event is a Keyboard event, focus will automatically be restored back to the first focusable node of the activator node.
If no activator node is set via setActivatorNodeRef, focus will automatically be restored on the first focusable node of the draggable node registered via setNodeRef.
Over
over
If you'd like to change the appearance of the draggable element in response to it being dragged over a different droppable container, check whether the over value is defined. 
If a draggable element is moved over a droppable area, the over property will be defined for all draggable elements, regardless of whether or not those draggable elements are active or not.
If you'd like to make changes to only the active draggable element in response to it being moved over a droppable area, check whether the isDragging property is true.
Transform
After a draggable item is picked up, the transform property will be populated with the translate coordinates you'll need to move the item on the screen.  
The transform object adheres to the following shape: 
1
{
2
  x: number;
3
  y: number;
4
  scaleX: number;
5
  scaleY: number;
6
}
Copied!
The x and y coordinates represent the delta from the point of origin of your draggable element since it started being dragged.
The scaleX and scaleY properties represent the difference in scale between the element that is currently being dragged and the droppable it is currently over, which can be useful if the draggable item needs to be dynamically resized to the size of the droppable it is over.