[Doc Update] About parent DOM Node

[alexandermirzoyan]

What about mentioning that <Draggable /> component should have single child DOM node instead of <Fragment />.

I think others can also face on such kind of problem, if needed I can open PR with updated documentation.

[STRML]

This was generated by AI during triage.

Agent Brief

Category: enhancement
Summary: Document that <Draggable> needs exactly one child that renders a DOM element, not a Fragment.

Current behavior:
Draggable calls React.Children.only(children) and clones that child with added className, style (the transform), and transform (SVG) props. A Fragment passes Children.only, but a Fragment has no DOM node, so the cloned props are dropped and nothing moves. The same happens with a custom component that does not forward className and style to its root element. The README does not say this.

Desired behavior:
The README states the child contract near the top of the <Draggable> usage docs. The child must be a single element, not a Fragment. If it is a custom component, that component must forward style, className, and (for nodeRef use) the ref to its root DOM element. Include one short correct example and one incorrect example.

Acceptance criteria:

• The README has a short "Child requirements" note (or similar) covering Fragments and custom components.
• The examples in the note match the current API (nodeRef usage).

Out of scope:

• A runtime dev warning for Fragments. File that separately if wanted.