@umriss-ui/schedule 0.43.0 → 0.44.0

package/CHANGELOG.md

@@ -18,6 +18,21 @@ moves from here under the rule above.
 
 ---
 
+## 0.44.0 – Malformed data says so, and the handle goes (Oct. 2026)
+
+### Added
+
+- **Malformed data warns once per cause in development:** a span that does not end after it starts, an item on an undeclared lane, an unknown task or dependency end, an id that stands twice. The checks run only in development.
+
+### Changed
+
+- **`ScheduleHandle` and the handle ref are removed;** 0.43.0 deprecated them. A `Schedule` ref is typed `HTMLDivElement`, and `positionAt`, `clientPointOf` and `visibleDomain` are on `useSchedule`'s return.
+  - Migration: replace `ref.current.positionAt(x, y)` with `positionAt(x, y)` from `const { positionAt } = useSchedule()`, and the same for `clientPointOf` and `visibleDomain`; type a ref as `HTMLDivElement`.
+- **`ariaLabel` on `Schedule` is removed;** 0.43.0 renamed it `aria-label`.
+  - Migration: write `aria-label` (TypeScript flags every use of `ariaLabel`).
+- **The peer ranges on core and charts move to `^0.44.0`.**
+  - Migration: install the 0.44 versions of `@umriss-ui/core` and `@umriss-ui/charts` beside it.
+
 ## 0.43.0 – A schedule that fills its frame, and takes a finger (Oct. 2026)
 
 ### Added

package/README.md

@@ -60,6 +60,8 @@ export function Plan() {
 }
 ```
 
+Malformed data - a subtask that does not end after it starts, an item on a lane no `Lane` declares, a dependency naming no subtask, an id that stands twice - warns in development, once per cause, and is left out in production. An application with imported data checks it where it imports it.
+
 ## Editing is controlled
 
 The schedule draws the data it is given and changes none of it (ADR-0023). A

package/dist/index.d.ts

@@ -2,7 +2,6 @@ import { CalendarInput } from '@umriss-ui/charts';
 import { HTMLAttributes } from 'react';
 import { ReactNode } from 'react';
 import { Ref } from 'react';
-import { RefObject } from 'react';
 
 /** The subtask as the intent asks for it. An intent for another subtask leaves
  it as it is. */
@@ -346,25 +345,6 @@ export declare interface ResolvedAppearance {
  bounded number of pushes instead of running on. */
 export declare function ripple(subtasks: readonly Subtask[], dependencies: readonly Dependency[], intent: Intent): MoveIntent[];
 
-/** What a schedule offers a caller imperatively: the arithmetic between a
- point on the screen and a time on a lane. Everything else is props.
- @deprecated since 0.43 - use the functions on `useSchedule`'s return. */
-export declare interface ScheduleHandle {
-    /** The time and the lane at a client point, or null outside the plot. */
-    positionAt: (clientX: number, clientY: number) => {
-        time: number;
-        lane: string | null;
-    } | null;
-    /** The client point of a time - on the middle of a lane where one is named -
-     or null while the schedule is not on screen. */
-    clientPointOf: (time: number, lane?: string) => {
-        x: number;
-        y: number;
-    } | null;
-    /** The visible span, as two wall-clock instants. */
-    visibleDomain: () => readonly [number, number];
-}
-
 /** What a pointer is on. */
 export declare type ScheduleHit = {
     readonly kind: "subtask";
@@ -416,10 +396,8 @@ export declare interface ScheduleOptions {
 }
 
 declare interface ScheduleOwnProps extends Omit<HTMLAttributes<HTMLDivElement>, "children" | "aria-label"> {
-    /** Receives the root element. A ref to the deprecated `ScheduleHandle` still
-     works for one more minor release: the element carries its three
-     functions. */
-    ref?: Ref<HTMLDivElement> | RefObject<ScheduleHandle | null> | undefined;
+    /** Receives the root element. */
+    ref?: Ref<HTMLDivElement> | undefined;
     /** Height in CSS pixels, both bands included, fixed. Left out, the schedule
      fills its frame - a stretched grid cell, a card the grid stretches, a
      container of definite height - and never goes below 400 px, which is also
@@ -593,17 +571,10 @@ export declare interface ScheduleParts {
  reads itself. `ref`, `className`, `style` and the rest reach the root; the
  name (`aria-label`, `aria-labelledby`) reaches the figure root and the plot,
  and a `aria-describedby` of yours is joined to the plot's summary. */
-export declare type ScheduleProps = ScheduleOwnProps & ({
+export declare type ScheduleProps = ScheduleOwnProps & {
     /** What the schedule shows, for a screen reader: "Plan of week 38". */
     "aria-label": string;
-    /** @deprecated since 0.43 - use `aria-label`. */
-    ariaLabel?: string;
-} | {
-    "aria-label"?: undefined;
-    /** What the schedule shows, for a screen reader.
-     @deprecated since 0.43 - use `aria-label`. */
-    ariaLabel: string;
-});
+};
 
 /** What a tooltip is about: the hovered subtask or dependency, with what the
  schedule knows about it. */