@dashfoo/core 0.1.0 → 0.3.0

package/README.md

@@ -186,6 +186,7 @@ call them directly for custom drag logic.
 
 ```ts
 resolveDockTarget(pointer, rect, opts?): DockTarget;
+dockZonePolygons(rect, opts?): Array<DockZone>;
 zoneRect(rect, location): Rect;
 ```
 
@@ -196,6 +197,13 @@ corners). It accepts `{ bandFraction }` to tune the band. `zoneRect` returns the
 region the dock indicator highlights for a `DockLocation`: the whole tabset for a
 `center` stack, the matching half for a split. `Point` and `Rect` are exported.
 
+`dockZonePolygons` enumerates the full hit-region partition behind
+`resolveDockTarget` as five polygons (`{ location, points }`): the inner center
+rect and four edge trapezoids whose seams run from each rect corner to the
+matching inner corner. The two functions share the band default, so a map
+painted from the polygons always agrees with the live hit-test — use it to
+visualize drop zones or to build custom drop indicators.
+
 ## History (undo / redo)
 
 A small `past` / `present` / `future` structure that wraps the reducer. `present`
@@ -214,7 +222,7 @@ if (canRedo(history)) history = redo(history);
 Every dispatched action is its own undo step; there is no coalescing. A splitter
 drag still lands as one step because react-resizable-panels v4 commits a single
 `adjustSplit` when the drag is released, not a per-frame stream. Any new dispatch
-clears the redo `future`.
+clears the redo `future`. History keeps the most recent `HISTORY_LIMIT` (100) steps; older snapshots are dropped.
 
 ## Serialize
 
@@ -261,9 +269,11 @@ const current = actor.getSnapshot().context.history.present;
 The drag/dock interaction lifecycle (`idle` → `dragging` → `idle`), driven by
 abstract events the dnd-kit adapter maps from pointer and keyboard input. It owns
 transient drag state only and never touches the document. On a valid `DROP` it
-**emits** a `COMMIT` carrying a `moveNode` action (the drag subject is a tab) or a
-`moveTabset` action (the subject is a whole tabset, dragged by its grip), which
-the React layer forwards to `dashfooMachine`.
+**emits** a `COMMIT` carrying a `moveNode` action (the drag subject is a tab), a
+`moveTabset` action (the subject is a whole tabset, dragged by its grip), or an
+`addNode` action (an `external` subject — content dragged in from outside the
+layout, carrying the `TabNode` to insert), which the React layer forwards to
+`dashfooMachine`.
 
 | Event    | Payload              |
 | -------- | -------------------- |
@@ -295,8 +305,8 @@ the React layer forwards to `dashfooMachine`.
 `findAttributedNode`, `findTabsetParent`, `findDuplicateIds`;
 types `AttributedNode`, `TabContainer`, `TabLocation`.
 
-`geometry` — `resolveDockTarget`, `zoneRect`; types `DockTarget`,
-`BandOptions`, `Point`, `Rect`.
+`geometry` — `resolveDockTarget`, `dockZonePolygons`, `zoneRect`; types
+`DockTarget`, `DockZone`, `BandOptions`, `Point`, `Rect`.
 
 `history` — `createHistory`, `dispatch`, `undo`, `redo`, `canUndo`, `canRedo`;
 type `History`.