@hirobius/design-system 0.19.1 → 0.21.0

package/dist/types/src/app/layouts/HdsDocsShell.d.ts

@@ -1,72 +0,0 @@
-/**
- * HdsDocsShell — three-region docs shell (left nav rail, content, right TOC
- * rail), driven by grid columns that default to 0 and are set per breakpoint.
- * @category Layout
- * @tier pattern
- * @public
- *
- * hds#280 slice: this is the SHELL MECHANICS ONLY — the smallest shippable
- * piece of the docs-shell epic. It ships:
- *
- *   - A 3-column grid (`leftRail | content | rightRail`), both rail columns
- *     defaulting to `0px` and set to `semantic.space.sidebar.railWidth`
- *     (hds#280 token, our own 280px — not HeroUI's 268px) per breakpoint via
- *     Tailwind's arbitrary-property + responsive-variant syntax, the same
- *     technique Fumadocs/HeroUI uses. `md768:` brings in the left rail,
- *     `xl1280:` brings in the right rail — matching the three-stage table in
- *     hds#280.
- *   - Each rail is `position: sticky` and scrolls independently of content
- *     and of the other rail, clipped to the viewport minus `topOffset`.
- *   - `topOffset` composes (it is one CSS length a caller supplies, e.g. its
- *     own sticky header's height token) rather than a hardcoded pixel value —
- *     the first stage of the row-cascade pattern hds#280 asks for. A second
- *     region (a tabs row, hds#280's PR-comment addendum) would extend this by
- *     adding its own height into the same `calc()` chain, not by hardcoding a
- *     second offset.
- *
- * Deliberately NOT in this slice (tracked as proposed follow-up issues, not
- * filed — see the PR/commit this ships in):
- *   - Below the TOC breakpoint, `rightRail` is omitted from the grid rather
- *     than becoming a reachable popover. The DoD explicitly wants a popover,
- *     not "merely hidden" — that is real, separate UI work (a sticky
- *     current-section breadcrumb bar), not shell mechanics.
- *   - Left-rail collapsible groups (chevron, active-section pill) and
- *     right-rail active-anchor styling (vertical rule, filled pill) are
- *     content the caller supplies via `leftRail`/`rightRail` — this shell
- *     does not build SideNav/Disclosure/NavItem composition for the caller.
- *   - `check-rendered-geometry` verification at every breakpoint in the DoD's
- *     table (needs a built Storybook + a live run, not exercised here).
- *   - Named CSS `grid-template-areas` (the DoD's literal ask) — this ships a
- *     3-column grid with DOM order instead, which is behaviorally identical
- *     for a single linear row of regions and needs no separate stylesheet.
- *     Areas earn their keep once a 4th region (a tabs row spanning full
- *     width) is added — call out then, not before.
- */
-import * as React from 'react';
-/** @public */
-export interface HdsDocsShellProps {
-    /** Left nav rail. Hidden below the `md768` breakpoint (grid column width 0). */
-    leftRail?: React.ReactNode;
-    /** Main content column. Always rendered, always fluid. */
-    children: React.ReactNode;
-    /**
-     * Right "on this page" rail. Hidden below the `xl1280` breakpoint (grid
-     * column width 0) — see the deferred-popover note above; it is REMOVED
-     * from the grid at that breakpoint, not merely visually hidden, so no
-     * hidden interactive content sits in the DOM unreachable.
-     */
-    rightRail?: React.ReactNode;
-    /**
-     * CSS length a caller supplies for a sticky header ABOVE this shell (e.g.
-     * TopNav's height token), so each rail's sticky offset and scrollable
-     * height compose against it instead of assuming the shell owns the whole
-     * viewport. Defaults to `'0px'`.
-     */
-    topOffset?: string;
-    /** Escape hatch: only for narrow layout adjustments that don't belong in the primitive API. */
-    className?: string;
-    /** Escape hatch: only for narrow layout adjustments that don't belong in the primitive API. */
-    style?: React.CSSProperties;
-}
-/** @public */
-export declare const HdsDocsShell: React.ForwardRefExoticComponent<HdsDocsShellProps & React.RefAttributes<HTMLDivElement>>;

package/dist/types/src/app/layouts/HdsSystemDocLayout.d.ts

@@ -1,14 +0,0 @@
-import type { ReactNode } from 'react';
-import { type DocLayoutContentMaxWidth } from './DocLayout.js';
-/**
- * HdsSystemDocLayout — single centered content column for documentation pages.
- * Thin wrapper around DocLayout: takes only `contentSlot` and `contentMaxWidth`,
- * with no sidebar or nav region to pass one into. Not the three-column docs
- * shell (left rail + content + right rail) — that is tracked as its own shell
- * component (hds#280).
- * @public
- */
-export declare function HdsSystemDocLayout({ contentSlot, contentMaxWidth, }: {
-    contentSlot: ReactNode;
-    contentMaxWidth?: DocLayoutContentMaxWidth;
-}): import("react/jsx-runtime").JSX.Element;

package/dist/types/src/app/lib/hds-search.d.ts

@@ -1,45 +0,0 @@
-/** @internal — search engine behind the CommandPalette; not part of the public API. */
-/**
- * hds-search — the manifest search engine extracted from CommandPalette.
- *
- * A dependency-free subsequence + position scorer (think micro-fzf) over four
- * corpora drawn from `virtual:hds-manifest`: component specs, utilities, role
- * tokens, and curated foundation sections. Pure and side-effect-free — the
- * manifest is passed in, never read from a module global — so it is unit-tested
- * directly (see scripts/../tests/hds-search.test.ts) rather than through a
- * component test hook.
- *
- * Lifted from command-palette.tsx per ADR-011's review (deep module behind a
- * narrow interface): the UI shell now imports { buildIndex, rank } and owns no
- * search logic.
- */
-import type { ManifestSpec, RoleToken, SystemManifest } from '../data/manifest-types.js';
-export type { ManifestSpec, RoleToken, SystemManifest };
-export type ResultKind = 'component' | 'pattern' | 'template' | 'utility' | 'token' | 'section';
-export interface PaletteResult {
-    id: string;
-    label: string;
-    description: string;
-    kind: ResultKind;
-    /** Where Enter/click navigates — relative React Router path. */
-    to: string;
-    /** Source string used for fuzzy matching (lowercased). */
-    haystack: string;
-}
-export declare const KIND_LABEL: Record<ResultKind, string>;
-export declare const MAX_RESULTS = 30;
-export declare function sanitize(text: string): string;
-/** Build the searchable index from a manifest. Pure — pass the manifest in. */
-export declare function buildIndex(manifest: SystemManifest): PaletteResult[];
-/**
- * Subsequence + position scorer:
- *   - Every char in `query` must appear in order inside `haystack`.
- *   - Earlier matches score higher (heavy weight on first hit).
- *   - Adjacent-char streaks score higher (clustered matches).
- *   - Word-start hits get a bonus.
- *
- * Returns -Infinity if `query` is not a subsequence of `haystack`.
- */
-export declare function fuzzyScore(query: string, haystack: string): number;
-/** Rank items against a query. Empty query → a stable starter set. */
-export declare function rank(query: string, items: PaletteResult[]): PaletteResult[];

package/dist/types/src/app/lib/nav-active.d.ts

@@ -1,16 +0,0 @@
-/**
- * nav-active — the single active-state rule for navigation items.
- *
- * Previously this 3-line predicate was copy-pasted in three places (NavGroup,
- * and HDSLayout's NestedNavGroup + SideNavItem). Centralized here so "is this
- * nav item active?" has exactly one definition (ADR-017, Phase 4).
- */
-/**
- * Whether a nav item is active for the current path.
- *
- * - `exact`: the route must match precisely (e.g. `/` or a landing page that
- *   shares a prefix with its children).
- * - otherwise: active when the current path equals the item path OR is a
- *   descendant route (`/components` is active on `/components/actions`).
- */
-export declare function isNavItemActive(currentPath: string, itemPath: string, exact?: boolean): boolean;

package/dist/types/src/app/lib/navLevels.d.ts

@@ -1,4 +0,0 @@
-export type NavLevel = 'root' | 'section' | 'nested' | 'deep';
-export declare function getNavLevelInset(level: NavLevel): string;
-export declare function getNavLevelLeadingPadding(level: NavLevel): string;
-export declare function getNextNavLevel(level: NavLevel): NavLevel;