efficient-easel 24.1.0 → 25.0.0

package/dist/session-EsjORLQ0.d.ts

@@ -1,43 +0,0 @@
-import { P as Place } from './types-Dq180WRV.js';
-
-/**
- * The one drag in flight, shared by every surface of an editor — the Layers
- * tree, the canvas and the Add list (blueprint step 3.2).
- *
- * Native drag-and-drop does not let a drop target read what is being dragged
- * until the drop itself (the data is sealed during `dragover`), and a tree that
- * only knows about drags it started cannot take a block from the Add list. So
- * the surface that starts a drag writes it here and every surface reads it: a
- * block picked up on the canvas can land in the tree, a tile from the Add list
- * on either.
- *
- * `from` is where the thing sits now — absent for something new (an Add tile),
- * which is also why a new thing can never be a no-op drop.
- */
-
-type DragHeld<I> = {
-    /** The identity `keyOf` gave it — which row or box is the one being dragged. */
-    key: string;
-    item: I;
-    /** Where it sits now. Absent: it is new, from the Add list. */
-    from?: Place;
-};
-type DragSession<I> = {
-    /** The drag in flight, current at once (for event handlers). */
-    get: () => DragHeld<I> | null;
-    /** The drag as last TOLD to subscribers (for rendering — see below). */
-    shown: () => DragHeld<I> | null;
-    start: (held: DragHeld<I>) => void;
-    end: () => void;
-    subscribe: (listener: () => void) => () => void;
-};
-/**
- * `get()` is current the moment a drag starts — the drop targets read it on
- * their first `dragover`. SUBSCRIBERS hear about a start one tick later: the
- * browser takes the drag picture when the `dragstart` handlers return, and a
- * render in between (a row dimming, the handle hiding) would be in the picture.
- * An end is told at once.
- */
-declare function createDragSession<I>(): DragSession<I>;
-
-export { type DragSession as D, type DragHeld as a, createDragSession as c };