@local-civics/hub-ui 0.1.226 → 0.1.228

package/dist/index.d.ts

@@ -605,6 +605,18 @@ declare const LearningForm: (props: LearningFormProps) => JSX.Element;
 type LoaderProps = {
     isLoading?: boolean;
     children: React__default.ReactNode;
+    /** Spinner width/height in px. Defaults to 35 (the original, small size) when omitted. */
+    size?: number;
+    /** Tailwind stroke color class for the spinner. Defaults to "stroke-sky-300" (the original, low-contrast color) when omitted. */
+    strokeClassName?: string;
+    /**
+     * Optional contextual text rendered beneath the spinner (e.g. "Loading dashboard activity...").
+     * Omitting it preserves the original bare-spinner layout exactly; passing it switches to a
+     * centered column with a min-height floor, so the spinner+text pair reliably centers within the
+     * content pane instead of drifting toward whatever height the (still-loading, mostly empty)
+     * content happens to compute to.
+     */
+    label?: string;
 };
 /**
  * A component for content that is not ready to be displayed.
@@ -1128,6 +1140,10 @@ type BadgeItem = {
     weight: number;
     iconURL?: string;
     onClick?: () => void;
+    lessonIds?: string[];
+    inProgress?: boolean;
+    submittedLessons?: number;
+    totalLessons?: number;
 };
 type PathwayCriteria = Record<string, number>;
 type PathwayCategory = {
@@ -1268,9 +1284,9 @@ declare const PathwayDetail: (props: PathwayDetailProps) => JSX.Element;
  * shown on `PathwayDetail`, condensed into a record-style layout. Toggled alongside
  * `PathwayDetail` from `Pathway.tsx`, not a routed page of its own.
  *
- * In-progress badge activity is intentionally omitted: that classification depends on
- * `startedAt`, which isn't reliably populated without lesson-level data yet. Only completed
- * activity is shown until that's sorted out.
+ * In-progress badges are cross-referenced against this student's own submitted lesson answers
+ * (`badge.inProgress`/`submittedLessons`/`totalLessons`, computed in hub's `usePathway()`) rather
+ * than the badge's own possibly-unset `startedAt` flag alone.
  * @param props
  * @constructor
  */
@@ -1381,6 +1397,12 @@ type DashboardShellProps = {
     sidebar: React.ReactNode;
     topBar?: React.ReactNode;
     isLoading?: boolean;
+    /** Contextual text shown beneath the loading spinner (e.g. "Loading dashboard activity..."). Omit to keep the original bare-spinner loading state. */
+    loadingLabel?: string;
+    /** Spinner width/height in px while loading. Omit to keep the original small (35px) spinner. */
+    loadingSize?: number;
+    /** Tailwind stroke color class for the loading spinner. Omit to keep the original low-contrast default. */
+    loadingStrokeClassName?: string;
     children?: React.ReactNode;
 };
 /**
@@ -1390,6 +1412,10 @@ type DashboardShellProps = {
  * bare `AuthLayout` usage — `AuthLayout` itself is untouched, still used for non-student surfaces.
  * Renders the shared `Footer` at the bottom of the scrollable content, pinned to the viewport
  * bottom on short pages and pushed below content on long ones (standard sticky-footer behavior).
+ * On print (`window.print()`), the sidebar/topbar/footer chrome is hidden and the fixed-viewport
+ * height/overflow constraints are relaxed so the page content paginates naturally instead of being
+ * clipped to one screen's worth of height - no page opts into this, it's a universal print rule
+ * since no legitimate use case wants nav chrome printed alongside a page's content.
  * @param props
  * @constructor
  */