@umriss-ui/schedule 0.44.0 → 0.45.0

package/docs/llms-full.md

@@ -1,4 +1,4 @@
-# @umriss-ui/schedule 0.44.0
+# @umriss-ui/schedule 0.45.0
 
 > React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.
 
@@ -1666,11 +1666,11 @@ no subtask yet; the caller creates one, with its own identity, from
 
 #### Known limits
 
-- No dependency types, critical path or auto-scheduling: the application decides where work goes, the schedule shows the result and its findings ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md)).
+- No dependency types, critical path or auto-scheduling: the application decides where work goes, the schedule shows the result and its findings ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md)).
 - No milestones yet: a point in time on a lane has no mark of its own.
 - A dependency joins two subtasks of one task; dependencies across tasks are not yet possible.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md).
 
 ## Plan
 
@@ -2112,7 +2112,7 @@ The keys of [First schedule](#first-schedule) apply here.
 
 - A folded group shows no summary - no utilisation band, no bar spanning its work: a computed claim would look like a drawn fact ([ADR-0025](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0025-a-lane-group-is-structure-over-lanes-never-a-lane.md)).
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Subtasks
 
@@ -2976,7 +2976,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - No stacked layout on request yet: an overlap is always drawn offset, as the finding it is.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Dependencies
 
@@ -3346,9 +3346,9 @@ type DependencyEnds = "dot" | "none";
 
 #### Known limits
 
-- Only finish-to-start within one task; no dependency types and no critical path ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md)).
+- Only finish-to-start within one task; no dependency types and no critical path ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md)).
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Routes
 
@@ -5051,7 +5051,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - One task at a time: there is no multiple selection.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Interactions
 
@@ -6133,7 +6133,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - Only the view is shared - the span and the folded groups, not the selection, the hover or the vertical scroll.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Functions on the hook
 
@@ -6591,7 +6591,7 @@ The keys of [First schedule](#first-schedule) apply here.
 
 - Overlapping work is marked, not packed into sub-lanes; stacked overlap is not built yet.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md).
 
 ## Editing
 
@@ -6966,10 +6966,10 @@ From `Overlap` — the full table stands on [Findings as data](#findings-as-data
 
 #### Known limits
 
-- No undo: your application owns the data, and with it the history ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md)).
+- No undo: your application owns the data, and with it the history ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md)).
 - The keys move work in time only; a lane change needs the pointer.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Stretch, lead-in, lead-out
 
@@ -7141,7 +7141,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - A main time never becomes shorter than one raster step, or a minute without a raster.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Snapping
 
@@ -8000,7 +8000,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - A rule that changes while a drag runs is noticed at the drop, not before.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Ripple
 
@@ -8285,10 +8285,10 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 #### Known limits
 
-- No dependency types, slack or critical path: the schedule is no project-planning engine ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md)).
+- No dependency types, slack or critical path: the schedule is no project-planning engine ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md)).
 - A dependency joins subtasks of one task, so work of other tasks is never pushed.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.45.0/docs/adr/0032-what-umriss-is-not.md).
 
 ## Measuring
 
@@ -8851,12 +8851,12 @@ Used on [Scenarios](#scenarios) and [Ripple](#ripple).
 
 ##### `snapTime`
 
-`time` onto the nearest line of the raster in local time - a step alone
-starts at local midnight. A step of zero or less is no raster: the time
-stays as it is.
+`time` onto the nearest line of the raster in the zone's time, the reader's
+unless one is named - a step alone starts at the zone's midnight. A step of
+zero or less is no raster: the time stays as it is.
 
 ```ts
-function snapTime(time: number, raster: number | SnapRaster): number;
+function snapTime(time: number, raster: number | SnapRaster, timeZone?: string): number;
 ```
 
 Used on [Snapping](#snapping).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@umriss-ui/schedule",
-  "version": "0.44.0",
+  "version": "0.45.0",
   "description": "React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.",
   "license": "MIT",
   "author": "Roman Händler",
@@ -59,8 +59,8 @@
     }
   },
   "peerDependencies": {
-    "@umriss-ui/charts": "^0.44.0",
-    "@umriss-ui/core": "^0.44.0",
+    "@umriss-ui/charts": "^0.45.0",
+    "@umriss-ui/core": "^0.45.0",
     "react": ">=19",
     "react-dom": ">=19"
   },
@@ -76,8 +76,8 @@
     "typescript": "^5.6.3",
     "vite": "^6.0.0",
     "vite-plugin-dts": "^4.3.0",
-    "@umriss-ui/charts": "0.44.0",
-    "@umriss-ui/core": "0.44.0",
+    "@umriss-ui/charts": "0.45.0",
+    "@umriss-ui/core": "0.45.0",
     "@umriss-ui/demo": "0.0.0"
   },
   "scripts": {