@eifi1/ui-kit 0.53.0 → 0.55.0

package/src/components/trigger-aria.ts

@@ -1,44 +0,0 @@
-// Internal — not re-exported from the barrel. Shared by the pickers whose trigger is
-// a `role="combobox"` button inside a wrapper: DatePicker, DateRangePicker, MonthPicker.
-
-/**
- * The attributes that NAME or DESCRIBE a field, which belong on its trigger — the
- * element a `<label htmlFor>`, a form library's control slot or an error message has
- * to reach. They used to land on the wrapper `<div>` with the rest of the caller's
- * props, so an external label named nothing and a form library's `aria-describedby`
- * pointed a screen reader at an element with no role (kastlan, 0.5.0).
- */
-export interface TriggerAria {
-  id?: string;
-  "aria-label"?: string;
-  "aria-labelledby"?: string;
-  "aria-describedby"?: string;
-  "aria-invalid"?: boolean | "true" | "false" | "grammar" | "spelling";
-  /** 0.23.0: a form library's `required` (RhfMonthPicker) is announced on the trigger,
-   *  not lost on the wrapper. */
-  "aria-required"?: boolean | "true" | "false";
-}
-
-/** Split a field's props into what its trigger takes and what its wrapper takes. */
-export function splitTriggerAria<T extends TriggerAria>(props: T): [TriggerAria, Omit<T, keyof TriggerAria>] {
-  const {
-    id,
-    "aria-label": label,
-    "aria-labelledby": labelledBy,
-    "aria-describedby": describedBy,
-    "aria-invalid": invalid,
-    "aria-required": required,
-    ...rest
-  } = props;
-  return [
-    {
-      id,
-      "aria-label": label,
-      "aria-labelledby": labelledBy,
-      "aria-describedby": describedBy,
-      "aria-invalid": invalid,
-      "aria-required": required,
-    },
-    rest,
-  ];
-}

package/src/components/use-anchor-dir.ts

@@ -1,20 +0,0 @@
-import { useLayoutEffect, useState } from "react";
-import type { RefObject } from "react";
-import { dirOf, type Direction } from "../lib/direction";
-
-/**
- * The reading direction at a portalled panel's anchor — internal, not exported from
- * the barrel. The field pickers' panels are portalled to `<body>`, out of the subtree
- * their `dir` came from, so they carry it across on their own root.
- *
- * Read in a layout effect while `open`, rather than off the ref during render: the
- * anchored rect these panels also wait for is measured the same way, so the panel's
- * first painted frame already has both, and a render never reads a ref.
- */
-export function useAnchorDir(ref: RefObject<Element | null>, open: boolean): Direction {
-  const [dir, setDir] = useState<Direction>("ltr");
-  useLayoutEffect(() => {
-    if (open) setDir(dirOf(ref.current));
-  }, [open, ref]);
-  return dir;
-}

package/src/components/use-mobile-reveal.ts

@@ -1,62 +0,0 @@
-import { useEffect, useRef, useState } from "react";
-
-/**
- * The phone's endless scroll, in place of the desktop pager (feedback #232).
- *
- * A client-side table already holds every row, so there is nothing to fetch — it simply
- * reveals more of the sorted list as a sentinel scrolls into view. A SERVER-paginated
- * table keeps its pager instead, because the rest of the rows genuinely are not here.
- *
- * The reveal count only ever grows and self-caps at the (re-filtered) list length, which
- * is why nothing resets it: narrowing a filter cannot leave the limit pointing past the
- * end, and widening one does not have to re-reveal what the user already scrolled past.
- *
- * `paginated={false}` opts out entirely: a table that is short by construction (an
- * invoice's line items) renders every row on a phone too. It used to be chunked here
- * regardless, so a twelve-line invoice showed its first ten lines and a "Loading…"
- * sentinel for rows that were already in memory.
- *
- * Lifted out of `DataTable` with the rest of its state; the sentinel ref belongs to the
- * caller's `<li>`.
- */
-export function useMobileReveal<T>({
-  rows,
-  slice,
-  isServer,
-  isMdUp,
-  unpaged = false,
-  defaultPageSize,
-}: {
-  /** The whole sorted list — what there is to reveal. */
-  rows: T[];
-  /** What a server-paginated table shows instead. */
-  slice: T[];
-  isServer: boolean;
-  isMdUp: boolean;
-  /** `paginated={false}` on a client-side table: show every row, reveal nothing. */
-  unpaged?: boolean;
-  defaultPageSize: number;
-}) {
-  const [mobileLimit, setMobileLimit] = useState(defaultPageSize);
-  const mobileSlice = isServer ? slice : unpaged ? rows : rows.slice(0, mobileLimit);
-  const canRevealMoreMobile = !isServer && !unpaged && !isMdUp && mobileLimit < rows.length;
-  const loadMoreRef = useRef<HTMLLIElement | null>(null);
-
-  useEffect(() => {
-    if (!canRevealMoreMobile) return;
-    const el = loadMoreRef.current;
-    if (!el || typeof IntersectionObserver === "undefined") return;
-    const io = new IntersectionObserver(
-      (entries) => {
-        if (entries.some((e) => e.isIntersecting)) {
-          setMobileLimit((n) => n + (defaultPageSize || 25));
-        }
-      },
-      { rootMargin: "300px" },
-    );
-    io.observe(el);
-    return () => io.disconnect();
-  }, [canRevealMoreMobile, mobileLimit, defaultPageSize]);
-
-  return { mobileSlice, canRevealMoreMobile, loadMoreRef };
-}