hazo_ui 6.3.1 → 6.5.0

package/CHANGE_LOG.md

@@ -5,6 +5,91 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## v6.5.0 (2026-08-02)
+
+### Added — swimlanes for `HazoUiKanban`
+
+A board can now declare `lanes`, rendering one full-width row per lane —
+a wide lane heading, then that lane's own copy of the whole column grid. Where
+`sections` (v6.4.0) group *within* a column, lanes group *across* all of them,
+so the second axis can be the row axis instead of the inner one.
+
+- `HazoUiKanbanProps.lanes?: KanbanLane[]` — `{ key, title, accepts?,
+  collapseWhenEmpty? }`. Cards are placed by the new `KanbanItem.laneKey`.
+  Omit `lanes` and nothing changes: existing boards render exactly as before.
+- `KanbanMoveEvent` gained `fromLane`/`toLane`; `KanbanReorderEvent` gained
+  `laneKey`. Move-vs-reorder is now decided on all three axes — same column,
+  section *and* lane is a reorder; changing any one is a move.
+- **A lane heading is the lane-only drop target.** It carries a lane but no
+  column, read as "change the lane, keep the card's column" — the mirror of a
+  sectioned column's head ("change the column, keep the section").
+- `collapseWhenEmpty` renders a lane with no cards as a thin full-width dashed
+  strip, which is what makes "declare every lane" affordable for a long
+  vocabulary. A card whose `laneKey` matches no declared lane renders in an
+  unlabelled trailing lane rather than disappearing.
+- The optimistic overlay tracks the destination lane too, so a cross-lane drop
+  moves immediately instead of snapping back until the consumer's async commit
+  lands.
+
+### Fixed — drops landed in the wrong column on tall or scrolled boards
+
+Two long-standing defects in drop resolution, both of which lanes made
+impossible to miss:
+
+- **Collision detection is now pointer-first** (`pointerWithin`, falling back
+  to `rectIntersection`, then `closestCorners`). `closestCorners` alone
+  averages the distance to all four corners, so a column stretched tall by a
+  neighbour's card stack scored *worse* than a short, far-away column — a drop
+  well inside the right column could resolve to a different one entirely.
+  Keyboard drags have no pointer and take the same fallbacks as before.
+- **Droppable ids are scoped per layout tree.** The mobile tab strip and the
+  desktop grid both always render (CSS hides one), so every column previously
+  registered twice under one id. dnd-kit keys its registry by id, so one node
+  won and collisions were measured against the CSS-hidden copy's 0×0 rect.
+  Ids now carry the tree ("m"/"d") and, on a laned board, the lane.
+
+## v6.4.0 (2026-08-01)
+
+### Added — in-column sections for `HazoUiKanban`
+
+A kanban column can now declare `sections`, splitting its body into
+separator-headed bands so a board can group on two axes at once (e.g. status
+across, tag down) without a mode toggle between them.
+
+- `KanbanColumn.sections?: KanbanSection[]` — `{ key, title, accepts?,
+  collapseWhenEmpty? }`. Cards are placed by the new
+  `KanbanItem.sectionKey`. Omit `sections` and nothing changes: existing
+  boards render exactly as before.
+- Each band is its own droppable, so a single drop expresses both column and
+  section. `KanbanMoveEvent` gained `fromSection`/`toSection`, and
+  `KanbanReorderEvent` gained `sectionKey`.
+- Move-vs-reorder is now decided on both axes — same column *and* same
+  section is a reorder; changing either is a move. Unsectioned boards have
+  `undefined` on both sides, so this collapses to the previous behaviour.
+- On a sectioned column the **header becomes a droppable** carrying the
+  column but no section — the status-only drop target ("move column, keep
+  section"). Required, not cosmetic: section bands cover the column body and
+  win every `closestCorners` contest, so without it a sectioned column has no
+  reachable spot that isn't a band. Unsectioned columns keep an inert header.
+- `collapseWhenEmpty` renders a section with no cards as a thin dashed drop
+  strip at the foot of the column. This is what makes "declare every section
+  in every column" practical for a long vocabulary: every section stays a
+  drop target without filling the column with empty headers.
+- The optimistic overlay tracks the destination section too, so a
+  same-column cross-section drop moves immediately rather than snapping back
+  until the consumer's async commit lands.
+- Dropping on a column's own padding leaves the card's section alone; a card
+  whose `sectionKey` matches no declared section renders in an unlabelled
+  trailing group rather than disappearing.
+
+New styling hooks (no new CSS variables): `cls_hazo_kanban_section`,
+`_section_head`, `_section_title`, `_section_rule`, `_section_count`,
+`_section_body`, `_section_empty`, `_section_over`, `_section_strips`,
+`cls_hazo_kanban_column_head_over`,
+`_section_strip`, `_section_strip_over`, `_section_unmatched`.
+
+Demo: test-app `/kanban` §10.
+
 ## v6.3.1 (2026-07-29)
 
 ### Fixed — test-app builds again

package/README.md

@@ -3677,6 +3677,48 @@ function Actions({ initial }) {
 event carries `revert()` — call it when your API request fails and the
 overlay snaps back to whatever `items` says.
 
+### Grouping: sections (v6.4.0) and swimlanes (v6.5.0)
+
+A board can group on a second axis, either *inside* each column or *across*
+all of them. Both are opt-in; omit them and the board is a plain column grid.
+
+```tsx
+// Sections: separator-headed bands inside each column, keyed by item.sectionKey
+<HazoUiKanban
+  columns={COLUMNS.map(col => ({
+    ...col,
+    sections: TAGS.map(t => ({ key: t, title: t, collapseWhenEmpty: true })),
+  }))}
+  items={items.map(it => ({ ...it, sectionKey: it.tag }))}
+  onMove={(e) => save(e.itemId, { column: e.toColumn, tag: e.toSection })}
+  renderCard={renderCard}
+/>
+
+// Swimlanes: one full-width row per lane, each with its own column grid,
+// keyed by item.laneKey
+<HazoUiKanban
+  columns={COLUMNS}
+  lanes={TAGS.map(t => ({ key: t, title: t, collapseWhenEmpty: true }))}
+  items={items.map(it => ({ ...it, laneKey: it.tag }))}
+  onMove={(e) => save(e.itemId, { column: e.toColumn, tag: e.toLane })}
+  renderCard={renderCard}
+/>
+```
+
+| | Sections | Lanes |
+|---|---|---|
+| Declared on | `KanbanColumn.sections` | `HazoUiKanbanProps.lanes` |
+| Card placed by | `KanbanItem.sectionKey` | `KanbanItem.laneKey` |
+| Renders as | bands stacked inside one column | full-width rows, each with the whole column grid |
+| Move event carries | `fromSection`/`toSection` | `fromLane`/`toLane` |
+| "Keep the other axis" drop target | the column head | the lane heading |
+| `collapseWhenEmpty` | thin drop strip at the column's foot | full-width drop strip |
+
+A drop expresses both axes at once, so one gesture can change status and tag
+together. `accepts(item)` on a column, section or lane rejects a drop into it.
+Cards whose key matches nothing declared render in an unlabelled trailing
+group (sections) or lane row (lanes) rather than disappearing.
+
 ### Theming (CSS custom properties)
 
 | Variable | Default | Purpose |