@stapel/workspaces-react 0.17.0 → 0.19.1

package/src/nav/manifest.ts

@@ -0,0 +1,120 @@
+/**
+ * This pair's contribution to the scripted-fullstack nav contract
+ * (`@stapel/core`'s `NavEntry`/`PackageNavManifest`). `scripts/gen-nav-
+ * manifest.mjs` reads `navEntries` below, stamps `package`/`version` from THIS
+ * package's own `package.json` (never hand-copied here — a version bump must
+ * not require touching this file), and emits
+ * `packages/workspaces-react/nav-manifest.json` plus this package's slice of
+ * the root aggregate.
+ *
+ * ## The six doors
+ *
+ *  - `workspaces.list` — the workspace roster (`<WorkspacesPage/>`), under the
+ *    container-synthesised `account.root` submenu, next to privacy and
+ *    billing. Everything it shows is the caller's own.
+ *  - `workspaces.settings` / `.members` / `.invitations` / `.audit` — the four
+ *    workspace-scoped admin screens, siblings of the roster under the same
+ *    account section, on paths RELATIVE to it (`workspaces/members`, …).
+ *  - `workspaces.invite` — the public `/invite/:token` route
+ *    (`<InviteAcceptPage/>`). `surface: "public"` and `requiresAuth: false`
+ *    because the invitee usually has no account here at all — that is the
+ *    entire reason `claim` exists — and the token in the URL is the bearer
+ *    secret. `menuVisibleDefault: false`: it is an address a letter sends
+ *    somebody to, never a menu item.
+ *
+ * ## Where the four scoped screens get their workspace (architecture verdict)
+ *
+ * They do NOT get it from the route. The active workspace is RUNTIME state —
+ * the same state the container writes when a person switches workspaces
+ * (`WorkspaceSelection.switchTo`) — not a path param of a settings URL, so
+ * these entries declare no `:workspaceId` segment and the screens read the
+ * selection themselves (`useOptionalWorkspaceSelection`, see
+ * `src/default/ActiveWorkspace.tsx`). A host that mounts the same components
+ * outside the shell keeps passing `workspaceId` explicitly; the prop stayed,
+ * it only became optional.
+ *
+ * The failure mode that made this a question at all — four doors opening on a
+ * screen with no workspace — is answered by the screens rather than by the
+ * contract: with no active workspace they render a designed "choose a
+ * workspace" state (and "you are not in a workspace yet" for a person who
+ * belongs to none), never a blank page and never a crash from a selection
+ * provider a shell forgot to wire.
+ */
+import type { NavEntry } from "@stapel/core";
+
+export const navEntries: readonly NavEntry[] = [
+  {
+    id: "workspaces.list",
+    labelKey: "workspaces.nav.workspaces",
+    icon: "AppstoreOutlined",
+    route: { path: "workspaces" },
+    component: { export: "WorkspacesPage", subpath: "default" },
+    placement: { level: "submenu", parentId: "account.root" },
+    menuVisibleDefault: true,
+    requiresAuth: true,
+    surface: "member",
+    order: 10,
+  },
+  {
+    id: "workspaces.settings",
+    labelKey: "workspaces.nav.settings",
+    icon: "ProfileOutlined",
+    route: { path: "workspaces/settings" },
+    component: { export: "WorkspaceSettings", subpath: "default" },
+    placement: { level: "submenu", parentId: "account.root" },
+    menuVisibleDefault: true,
+    requiresAuth: true,
+    surface: "member",
+    order: 11,
+  },
+  {
+    id: "workspaces.members",
+    labelKey: "workspaces.nav.members",
+    icon: "UserOutlined",
+    route: { path: "workspaces/members" },
+    component: { export: "MembersManager", subpath: "default" },
+    placement: { level: "submenu", parentId: "account.root" },
+    menuVisibleDefault: true,
+    requiresAuth: true,
+    surface: "member",
+    order: 12,
+  },
+  {
+    id: "workspaces.invitations",
+    labelKey: "workspaces.nav.invitations",
+    icon: "MessageOutlined",
+    route: { path: "workspaces/invitations" },
+    component: { export: "InvitationsPane", subpath: "default" },
+    placement: { level: "submenu", parentId: "account.root" },
+    menuVisibleDefault: true,
+    requiresAuth: true,
+    surface: "member",
+    order: 13,
+  },
+  {
+    id: "workspaces.audit",
+    labelKey: "workspaces.nav.audit",
+    icon: "AuditOutlined",
+    route: { path: "workspaces/audit" },
+    component: { export: "AuditTrailPane", subpath: "default" },
+    placement: { level: "submenu", parentId: "account.root" },
+    menuVisibleDefault: true,
+    requiresAuth: true,
+    surface: "member",
+    order: 14,
+  },
+  {
+    id: "workspaces.invite",
+    labelKey: "workspaces.nav.invite",
+    icon: "MessageOutlined",
+    route: { path: "/invite/:token" },
+    component: { export: "InviteAcceptPage", subpath: "default" },
+    placement: { level: "top" },
+    menuVisibleDefault: false,
+    // A session is NOT needed: the whole point of the claim path is that the
+    // invitee has no account yet, and decline went `AllowAny` in 0.27.0.
+    requiresAuth: false,
+    surface: "public",
+    order: 0,
+  },
+];

package/dist/default/ErrorAlert.d.ts

@@ -1,8 +0,0 @@
-import type { CSSProperties, ReactElement } from "react";
-import type { FlowErrorDisplay } from "@stapel/core";
-export declare function ErrorAlert(props: {
-    error: FlowErrorDisplay | undefined;
-    style?: CSSProperties | undefined;
-    testId?: string | undefined;
-}): ReactElement | null;
-//# sourceMappingURL=ErrorAlert.d.ts.map

package/dist/default/ErrorAlert.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"ErrorAlert.d.ts","sourceRoot":"","sources":["../../src/default/ErrorAlert.tsx"],"names":[],"mappings":"AAkBA,OAAO,KAAK,EAAE,aAAa,EAAE,YAAY,EAAE,MAAM,OAAO,CAAC;AACzD,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,cAAc,CAAC;AAErD,wBAAgB,UAAU,CAAC,KAAK,EAAE;IAChC,KAAK,EAAE,gBAAgB,GAAG,SAAS,CAAC;IACpC,KAAK,CAAC,EAAE,aAAa,GAAG,SAAS,CAAC;IAClC,MAAM,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;CAC7B,GAAG,YAAY,GAAG,IAAI,CAqBtB"}

package/dist/default/ErrorAlert.js

@@ -1,30 +0,0 @@
-import { jsx as _jsx } from "react/jsx-runtime";
-/**
- * The one error surface this pair's default skins render, so the split copy
- * core produces reaches a screen the same way everywhere.
- *
- * Core's `describeFlowError` splits a failure into the sentence a person
- * reads and the technical detail a support agent quotes (owner report
- * 2026-08-09: the status used to be spliced into the sentence, which ended
- * in a bare `" (500)"` — and a product does not read a protocol number out to
- * a person). The split is only worth anything if a
- * skin actually renders both halves at their own weights: `message` at
- * normal weight, `detail` muted and small, where an eye skips it and a
- * support agent finds it.
- *
- * `undefined` in — including a `detail` that core left `undefined` because
- * there was nothing worth quoting — renders nothing rather than an empty
- * muted line.
- */
-import { Alert, Typography } from "antd";
-export function ErrorAlert(props) {
-    const { error } = props;
-    if (!error)
-        return null;
-    return (_jsx(Alert, { type: "error", showIcon: true, ...(props.style ? { style: props.style } : {}), ...(props.testId ? { "data-testid": props.testId } : {}), message: error.message, ...(error.detail
-            ? {
-                description: (_jsx(Typography.Text, { type: "secondary", style: { fontSize: 12 }, children: error.detail })),
-            }
-            : {}) }));
-}
-//# sourceMappingURL=ErrorAlert.js.map

package/dist/default/ErrorAlert.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"ErrorAlert.js","sourceRoot":"","sources":["../../src/default/ErrorAlert.tsx"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;;;;GAgBG;AACH,OAAO,EAAE,KAAK,EAAE,UAAU,EAAE,MAAM,MAAM,CAAC;AAIzC,MAAM,UAAU,UAAU,CAAC,KAI1B;IACC,MAAM,EAAE,KAAK,EAAE,GAAG,KAAK,CAAC;IACxB,IAAI,CAAC,KAAK;QAAE,OAAO,IAAI,CAAC;IACxB,OAAO,CACL,KAAC,KAAK,IACJ,IAAI,EAAC,OAAO,EACZ,QAAQ,WACJ,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,KAAK,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,KAC3C,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,aAAa,EAAE,KAAK,CAAC,MAAM,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,EACzD,OAAO,EAAE,KAAK,CAAC,OAAO,KAClB,CAAC,KAAK,CAAC,MAAM;YACf,CAAC,CAAC;gBACE,WAAW,EAAE,CACX,KAAC,UAAU,CAAC,IAAI,IAAC,IAAI,EAAC,WAAW,EAAC,KAAK,EAAE,EAAE,QAAQ,EAAE,EAAE,EAAE,YACtD,KAAK,CAAC,MAAM,GACG,CACnB;aACF;YACH,CAAC,CAAC,EAAE,CAAC,GACP,CACH,CAAC;AACJ,CAAC"}

package/src/default/ErrorAlert.tsx

@@ -1,47 +0,0 @@
-/**
- * The one error surface this pair's default skins render, so the split copy
- * core produces reaches a screen the same way everywhere.
- *
- * Core's `describeFlowError` splits a failure into the sentence a person
- * reads and the technical detail a support agent quotes (owner report
- * 2026-08-09: the status used to be spliced into the sentence, which ended
- * in a bare `" (500)"` — and a product does not read a protocol number out to
- * a person). The split is only worth anything if a
- * skin actually renders both halves at their own weights: `message` at
- * normal weight, `detail` muted and small, where an eye skips it and a
- * support agent finds it.
- *
- * `undefined` in — including a `detail` that core left `undefined` because
- * there was nothing worth quoting — renders nothing rather than an empty
- * muted line.
- */
-import { Alert, Typography } from "antd";
-import type { CSSProperties, ReactElement } from "react";
-import type { FlowErrorDisplay } from "@stapel/core";
-
-export function ErrorAlert(props: {
-  error: FlowErrorDisplay | undefined;
-  style?: CSSProperties | undefined;
-  testId?: string | undefined;
-}): ReactElement | null {
-  const { error } = props;
-  if (!error) return null;
-  return (
-    <Alert
-      type="error"
-      showIcon
-      {...(props.style ? { style: props.style } : {})}
-      {...(props.testId ? { "data-testid": props.testId } : {})}
-      message={error.message}
-      {...(error.detail
-        ? {
-            description: (
-              <Typography.Text type="secondary" style={{ fontSize: 12 }}>
-                {error.detail}
-              </Typography.Text>
-            ),
-          }
-        : {})}
-    />
-  );
-}