@stapel/listings-react 0.3.1 → 0.7.0

package/src/model/mineSource.ts

@@ -1,55 +1,60 @@
 /**
- * THE GAP: stapel-listings cannot list a person their own listings.
+ * THE GAP, AND THE ROUTE THAT CLOSED IT.
  *
- * This is the one place in the pair where a contract is missing rather than
- * awkward, so it gets its own module and its own name.
+ * This file used to open "stapel-listings cannot list a person their own
+ * listings", and that was the only place in the pair where a contract was
+ * missing rather than awkward. `GET /listings/` answers `qs.published()` and
+ * takes no owner parameter (`views.ListingViewSet.get_queryset`): it returns
+ * the whole marketplace's shop window and can be narrowed to nobody. The only
+ * owner-scoped reads were `my/counters` (three integers) and `my/favorites`,
+ * so a seller's own DRAFTS were unreachable by any call the contract offered
+ * — and drafts are not indexed either, so routing around it through
+ * `@stapel/search-react`'s `owner=` would have returned the published subset
+ * and quietly called it "everything". The dashboard shipped with a
+ * host-injected source and NAMED the absence on screen, because "we cannot
+ * ask" and "you have no listings" are different sentences.
  *
- * `GET /listings/` answers `qs.published()` and takes no owner parameter
- * (`views.ListingViewSet.get_queryset`): it returns the whole marketplace's
- * shop window and can be narrowed to nobody. The only owner-scoped reads in
- * the module are `my/counters` (three integers) and `my/favorites`. So a
- * seller's own DRAFTS are unreachable by any call this contract offers — and
- * drafts are not indexed either, so routing around it through
- * `@stapel/search-react`'s `owner=` would return the published subset and
- * quietly call it "everything".
+ * **stapel-listings 0.7.0 answers it**: `GET /listings/my/listings/`, the
+ * caller's own rows in every status, `?status=` for a tab's set, the same
+ * `IDAnchorPagination` envelope the other two owner reads use. So
+ * {@link defaultMyListingsSource} is what the dashboard runs on now, and
+ * there is no failure state left to name — the missing-source error and its
+ * i18n key are gone rather than kept as a comment about a thing that no
+ * longer happens.
  *
- * The storefront spec assumed `GET /listings/` was "for mine" (§4.1). It is
- * not, and this pair records the gap rather than papering over it.
- *
- * Two upstream asks, in preference order:
- *  1. an `?owner=me` filter (or a `my/listings` action) on the list endpoint,
- *     with the same `IDAnchorPagination` envelope the other two use;
- *  2. failing that, a `status` filter on it, so at least the published subset
- *     can be narrowed without a search module.
- *
- * Until then a host injects a {@link MyListingsSource} and the dashboard
- * works completely; without one it shows the real counters and NAMES the
- * absence, because "we cannot ask" and "you have no listings" are different
- * sentences.
+ * {@link MyListingsSource} stays, as a seam and not as a workaround: a
+ * deployment that keeps its sellers' rows somewhere else (a read model, a
+ * legacy table, a host that has already fetched the page) hands one in and
+ * the dashboard renders it unchanged. What it must return is one page of the
+ * owner card — including the `moderation_status` and the `*_draft` twins,
+ * which is why the type is {@link PaginatedMyListingCards} and not the public
+ * card envelope.
  */
-import { StapelApiError } from "@stapel/core";
-import type { ListingPageParams, PaginatedListingCards } from "../api/types.js";
+import type { ListingsApi } from "../api/listingsApi.js";
+import type { MyListingsParams, PaginatedMyListingCards } from "../api/types.js";
 import type { MyListingsTab } from "./status.js";
-import { LISTINGS_I18N_KEYS } from "../i18n/keys.js";
+import { MY_LISTINGS_TAB_STATUSES } from "./status.js";
 
-/** One page of the caller's own listings, however the host can get them. */
+/** One page of the caller's own listings, however the host gets them. */
 export type MyListingsSource = (args: {
   readonly tab: MyListingsTab;
-  readonly page: ListingPageParams;
+  readonly page: MyListingsParams;
   readonly signal?: AbortSignal;
-}) => Promise<PaginatedListingCards>;
+}) => Promise<PaginatedMyListingCards>;
 
 /**
- * The error a dashboard without a source reports.
+ * The source the dashboard uses unless a host replaces it: the contract's own
+ * route, narrowed to the tab's statuses.
  *
- * `status: 0` on purpose: this is a fact about the deployment's wiring, not
- * something a server said, and a client-side refusal must never be
- * indistinguishable from one that came over the wire.
+ * The tab → statuses table is `MY_LISTINGS_TAB_STATUSES`, which is a copy of
+ * the SERVER's grouping in `views.my_counters`. That is the whole point: the
+ * rows this fetches and the count on the tab beside them are the same set,
+ * asserted upstream (`tests/test_my_listings.py`) and here.
  */
-export const MY_LISTINGS_SOURCE_MISSING: StapelApiError = new StapelApiError({
-  code: LISTINGS_I18N_KEYS.mineSourceMissing,
-  message:
-    "No MyListingsSource was supplied, and stapel-listings has no " +
-    "owner-scoped list endpoint to fall back on.",
-  status: 0,
-});
+export function defaultMyListingsSource(api: ListingsApi): MyListingsSource {
+  return ({ tab, page, signal }) =>
+    api.myListings(
+      { ...page, status: MY_LISTINGS_TAB_STATUSES[tab] },
+      signal !== undefined ? { signal } : {}
+    );
+}

package/src/model/mutations.ts

@@ -27,10 +27,13 @@ import { listingsQueryKeys } from "./queryKeys.js";
  * ── The invalidation rule ──────────────────────────────────────────────────
  *
  * A write that can move `status` or `moderation_status` invalidates the
- * DETAIL, the STATUS probe and the COUNTERS — the counters because their
- * three tabs are defined by status sets (`views.my_counters`), so a publish
- * silently moves a row from "drafts" to "active" and a dashboard that did not
- * refetch would show the old number beside the new row.
+ * DETAIL, the STATUS probe, the COUNTERS and the owner's ROWS — the counters
+ * because their three tabs are defined by status sets (`views.my_counters`),
+ * so a publish silently moves a row from "drafts" to "active" and a dashboard
+ * that did not refetch would show the old number beside the new row; the rows
+ * for the same reason, since stapel-listings 0.7.0 gave them a route and they
+ * are narrowed by exactly those status sets. Invalidating one and not the
+ * other is the shape of the bug where the badge says 2 and the tab shows 3.
  *
  * Nothing here is optimistic except the favourite toggle, and that exception
  * is argued at its own hook.
@@ -46,6 +49,7 @@ function invalidateListing(queryClient: QueryClient, id: number): void {
   void queryClient.invalidateQueries({
     queryKey: listingsQueryKeys.validateDraft(id),
   });
+  void queryClient.invalidateQueries({ queryKey: listingsQueryKeys.allMine() });
 }
 
 /** Start a draft. The server forces `owner` and `status=draft`. */
@@ -63,6 +67,9 @@ export function useCreateDraft(): UseMutationResult<
       void queryClient.invalidateQueries({
         queryKey: listingsQueryKeys.myCounters(),
       });
+      void queryClient.invalidateQueries({
+        queryKey: listingsQueryKeys.allMine(),
+      });
     },
   });
 }

package/src/model/queryKeys.ts

@@ -49,12 +49,17 @@ export const listingsQueryKeys: {
   myFavorites(
     page: ListingPageKey
   ): readonly ["listings", "my", "favorites", ListingPageKey];
-  /** The owner's own rows, per tab — see `headless/MyListings.tsx` for why
-   * this read goes through an injected source. */
+  /** The owner's own rows, per tab (`GET my/listings/?status=…`). */
   mine(
     tab: string,
     page: ListingPageKey
   ): readonly ["listings", "my", "listings", string, ListingPageKey];
+  /** The owner's rows no tab folds in — a takedown. A sibling of `mine` and
+   * not one of its tabs, because it answers a different question and must not
+   * be evicted when a tab pages. */
+  mineUntabbed(): readonly ["listings", "my", "listings", "untabbed"];
+  /** Every owner-row page, for an invalidation after a write. */
+  allMine(): readonly ["listings", "my", "listings"];
   /** `GET /{pk}/validate-draft/` — the dry run of a publish. */
   validateDraft(id: number): readonly ["listings", "validate-draft", number];
   /** Every favourites PAGE, for an invalidation after a toggle — the cursor
@@ -70,6 +75,8 @@ export const listingsQueryKeys: {
   myCounters: () => [ROOT, "my", "counters"],
   myFavorites: (page) => [ROOT, "my", "favorites", page],
   mine: (tab, page) => [ROOT, "my", "listings", tab, page],
+  mineUntabbed: () => [ROOT, "my", "listings", "untabbed"],
+  allMine: () => [ROOT, "my", "listings"],
   validateDraft: (id) => [ROOT, "validate-draft", id],
   allFavorites: () => [ROOT, "my", "favorites"],
   allLists: () => [ROOT, "list"],

package/src/model/status.ts

@@ -29,6 +29,7 @@
  * asserts the whole 9 × 4 table, so a state added upstream is a red test and
  * not a bare enum value on a page.
  */
+import { LISTING_STATUSES } from "../api/types.js";
 import type {
   ListingLifecycleStatus,
   ListingModerationStatus,
@@ -277,3 +278,17 @@ export function tabOf(
   }
   return undefined;
 }
+
+/**
+ * The statuses no tab folds in — `blocked`, and nothing else today.
+ *
+ * DERIVED, not written down a second time: a status added upstream and left
+ * out of the counter groupings lands here automatically and gets shown, which
+ * is the opposite of what a hardcoded `["blocked"]` would do the day it goes
+ * stale. The dashboard renders these rows OUTSIDE the tabs (see
+ * `default/MyListingsPane.tsx`) rather than folding them into one, because a
+ * tab's rows and its `my/counters` badge have to describe the same set — and
+ * `my/counters` counts a takedown in no tab at all.
+ */
+export const MY_LISTINGS_UNTABBED_STATUSES: readonly ListingLifecycleStatus[] =
+  LISTING_STATUSES.filter((status) => tabOf(status) === undefined);

package/dist/default/ErrorAlert.d.ts

@@ -1,9 +0,0 @@
-import type { CSSProperties, ReactElement, ReactNode } from "react";
-import type { FlowErrorDisplay } from "@stapel/core";
-export declare function ErrorAlert(props: {
-    error: FlowErrorDisplay | undefined;
-    style?: CSSProperties | undefined;
-    testId?: string | undefined;
-    action?: ReactNode;
-}): 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":"AAeA,OAAO,KAAK,EAAE,aAAa,EAAE,YAAY,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AACpE,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;IAC5B,MAAM,CAAC,EAAE,SAAS,CAAC;CACpB,GAAG,YAAY,GAAG,IAAI,CAsBtB"}

package/dist/default/ErrorAlert.js

@@ -1,27 +0,0 @@
-import { jsx as _jsx } from "react/jsx-runtime";
-/**
- * The one error surface this pair's default skin renders, so the split copy
- * core produces reaches a screen the same way everywhere (mirrors the
- * docs/notifications/workspaces etalon).
- *
- * 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, ending in a
- * bare `" (500)"`). The split only helps if a skin renders both halves at
- * their own weights: `message` at normal weight, `detail` muted and small.
- *
- * `undefined` in — including a `detail` core left `undefined` because there
- * was nothing worth quoting — renders nothing rather than an empty 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 } : {}), ...(props.action ? { action: props.action } : {}), 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;;;;;;;;;;;;;GAaG;AACH,OAAO,EAAE,KAAK,EAAE,UAAU,EAAE,MAAM,MAAM,CAAC;AAIzC,MAAM,UAAU,UAAU,CAAC,KAK1B;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,KACrD,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,MAAM,EAAE,KAAK,CAAC,MAAM,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,EAClD,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/dist/default/theme.d.ts

@@ -1,25 +0,0 @@
-import type { CSSProperties, ReactElement, ReactNode } from "react";
-import type { ThemeMode } from "@stapel/tokens-antd";
-export interface ListingsSkinThemeProps {
-    /**
-     * Light or dark. Defaults to the mode the host's document declares
-     * (`resolveThemeMode()`). Pass explicitly to pin a side.
-     */
-    readonly mode?: ThemeMode;
-    /** Extra styles merged onto the themed root element (layout only — colors
-     * come from the mode). */
-    readonly style?: CSSProperties;
-    readonly children: ReactNode;
-}
-/**
- * `<ListingsSkinTheme/>` — the self-theming wrapper of
- * `@stapel/listings-react/default`. Standalone use is supported (wrap any
- * composition of the skin's parts once); the shipped surfaces
- * (`ListingCard`, `ListingDetailPane`, `ListingComposerPage`,
- * `MyListingsPane`, `FavoritesPane`)
- * each already wrap themselves, and nested antd
- * `ConfigProvider`s merge, so composing them under one `ListingsSkinTheme`
- * stays correct.
- */
-export declare function ListingsSkinTheme(props: ListingsSkinThemeProps): ReactElement;
-//# sourceMappingURL=theme.d.ts.map

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

@@ -1 +0,0 @@
-{"version":3,"file":"theme.d.ts","sourceRoot":"","sources":["../../src/default/theme.tsx"],"names":[],"mappings":"AAgBA,OAAO,KAAK,EAAE,aAAa,EAAE,YAAY,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AAOpE,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,qBAAqB,CAAC;AAErD,MAAM,WAAW,sBAAsB;IACrC;;;OAGG;IACH,QAAQ,CAAC,IAAI,CAAC,EAAE,SAAS,CAAC;IAC1B;8BAC0B;IAC1B,QAAQ,CAAC,KAAK,CAAC,EAAE,aAAa,CAAC;IAC/B,QAAQ,CAAC,QAAQ,EAAE,SAAS,CAAC;CAC9B;AAED;;;;;;;;;GASG;AACH,wBAAgB,iBAAiB,CAAC,KAAK,EAAE,sBAAsB,GAAG,YAAY,CAmB7E"}

package/dist/default/theme.js

@@ -1,40 +0,0 @@
-import { jsx as _jsx } from "react/jsx-runtime";
-/**
- * The default skin's INTERNAL theme provider — every `/default` surface wraps
- * itself in this, so the skin is readable no matter what the host supplies
- * (tracker #26: a skin set with no internal provider once inherited a theme
- * bridge serving light-mode values inside a dark document — text on
- * background at 1.00:1). The theme derives from `@stapel/tokens` via
- * `@stapel/tokens-antd`'s `toAntdThemeConfig(mode)`; `mode` defaults to what
- * the HOST's document declares (`resolveThemeMode()` — the `data-theme`
- * attribute `tokens.css` keys its dark block on), never to a hardcoded side.
- *
- * This is also what "override styles" means for this pair: a storefront
- * retheming through the §68 token JSON regenerates its `--stapel-*` custom
- * properties and the result page follows with zero code — a far better deal
- * than a prop-per-colour API, and the reason the skin has none.
- */
-import { useMemo } from "react";
-import { ConfigProvider } from "antd";
-import { resolveThemeMode, toAntdTheme, toAntdThemeConfig, } from "@stapel/tokens-antd";
-/**
- * `<ListingsSkinTheme/>` — the self-theming wrapper of
- * `@stapel/listings-react/default`. Standalone use is supported (wrap any
- * composition of the skin's parts once); the shipped surfaces
- * (`ListingCard`, `ListingDetailPane`, `ListingComposerPage`,
- * `MyListingsPane`, `FavoritesPane`)
- * each already wrap themselves, and nested antd
- * `ConfigProvider`s merge, so composing them under one `ListingsSkinTheme`
- * stays correct.
- */
-export function ListingsSkinTheme(props) {
-    const mode = props.mode ?? resolveThemeMode();
-    const theme = useMemo(() => toAntdThemeConfig(mode), [mode]);
-    const token = useMemo(() => toAntdTheme(mode), [mode]);
-    return (_jsx(ConfigProvider, { theme: theme, children: _jsx("div", { "data-listings-skin-root": true, "data-listings-skin-mode": mode, style: {
-                color: token.colorText,
-                backgroundColor: token.colorBgContainer,
-                ...props.style,
-            }, children: props.children }) }));
-}
-//# sourceMappingURL=theme.js.map

package/dist/default/theme.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"theme.js","sourceRoot":"","sources":["../../src/default/theme.tsx"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;;GAcG;AACH,OAAO,EAAE,OAAO,EAAE,MAAM,OAAO,CAAC;AAEhC,OAAO,EAAE,cAAc,EAAE,MAAM,MAAM,CAAC;AACtC,OAAO,EACL,gBAAgB,EAChB,WAAW,EACX,iBAAiB,GAClB,MAAM,qBAAqB,CAAC;AAe7B;;;;;;;;;GASG;AACH,MAAM,UAAU,iBAAiB,CAAC,KAA6B;IAC7D,MAAM,IAAI,GAAG,KAAK,CAAC,IAAI,IAAI,gBAAgB,EAAE,CAAC;IAC9C,MAAM,KAAK,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC,iBAAiB,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,CAAC,CAAC;IAC7D,MAAM,KAAK,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC,WAAW,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,CAAC,CAAC;IACvD,OAAO,CACL,KAAC,cAAc,IAAC,KAAK,EAAE,KAAK,YAC1B,0EAE2B,IAAI,EAC7B,KAAK,EAAE;gBACL,KAAK,EAAE,KAAK,CAAC,SAAS;gBACtB,eAAe,EAAE,KAAK,CAAC,gBAAgB;gBACvC,GAAG,KAAK,CAAC,KAAK;aACf,YAEA,KAAK,CAAC,QAAQ,GACX,GACS,CAClB,CAAC;AACJ,CAAC"}

package/src/default/ErrorAlert.tsx

@@ -1,46 +0,0 @@
-/**
- * The one error surface this pair's default skin renders, so the split copy
- * core produces reaches a screen the same way everywhere (mirrors the
- * docs/notifications/workspaces etalon).
- *
- * 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, ending in a
- * bare `" (500)"`). The split only helps if a skin renders both halves at
- * their own weights: `message` at normal weight, `detail` muted and small.
- *
- * `undefined` in — including a `detail` core left `undefined` because there
- * was nothing worth quoting — renders nothing rather than an empty line.
- */
-import { Alert, Typography } from "antd";
-import type { CSSProperties, ReactElement, ReactNode } from "react";
-import type { FlowErrorDisplay } from "@stapel/core";
-
-export function ErrorAlert(props: {
-  error: FlowErrorDisplay | undefined;
-  style?: CSSProperties | undefined;
-  testId?: string | undefined;
-  action?: ReactNode;
-}): 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 } : {})}
-      {...(props.action ? { action: props.action } : {})}
-      message={error.message}
-      {...(error.detail
-        ? {
-            description: (
-              <Typography.Text type="secondary" style={{ fontSize: 12 }}>
-                {error.detail}
-              </Typography.Text>
-            ),
-          }
-        : {})}
-    />
-  );
-}

package/src/default/theme.tsx

@@ -1,67 +0,0 @@
-/**
- * The default skin's INTERNAL theme provider — every `/default` surface wraps
- * itself in this, so the skin is readable no matter what the host supplies
- * (tracker #26: a skin set with no internal provider once inherited a theme
- * bridge serving light-mode values inside a dark document — text on
- * background at 1.00:1). The theme derives from `@stapel/tokens` via
- * `@stapel/tokens-antd`'s `toAntdThemeConfig(mode)`; `mode` defaults to what
- * the HOST's document declares (`resolveThemeMode()` — the `data-theme`
- * attribute `tokens.css` keys its dark block on), never to a hardcoded side.
- *
- * This is also what "override styles" means for this pair: a storefront
- * retheming through the §68 token JSON regenerates its `--stapel-*` custom
- * properties and the result page follows with zero code — a far better deal
- * than a prop-per-colour API, and the reason the skin has none.
- */
-import { useMemo } from "react";
-import type { CSSProperties, ReactElement, ReactNode } from "react";
-import { ConfigProvider } from "antd";
-import {
-  resolveThemeMode,
-  toAntdTheme,
-  toAntdThemeConfig,
-} from "@stapel/tokens-antd";
-import type { ThemeMode } from "@stapel/tokens-antd";
-
-export interface ListingsSkinThemeProps {
-  /**
-   * Light or dark. Defaults to the mode the host's document declares
-   * (`resolveThemeMode()`). Pass explicitly to pin a side.
-   */
-  readonly mode?: ThemeMode;
-  /** Extra styles merged onto the themed root element (layout only — colors
-   * come from the mode). */
-  readonly style?: CSSProperties;
-  readonly children: ReactNode;
-}
-
-/**
- * `<ListingsSkinTheme/>` — the self-theming wrapper of
- * `@stapel/listings-react/default`. Standalone use is supported (wrap any
- * composition of the skin's parts once); the shipped surfaces
- * (`ListingCard`, `ListingDetailPane`, `ListingComposerPage`,
- * `MyListingsPane`, `FavoritesPane`)
- * each already wrap themselves, and nested antd
- * `ConfigProvider`s merge, so composing them under one `ListingsSkinTheme`
- * stays correct.
- */
-export function ListingsSkinTheme(props: ListingsSkinThemeProps): ReactElement {
-  const mode = props.mode ?? resolveThemeMode();
-  const theme = useMemo(() => toAntdThemeConfig(mode), [mode]);
-  const token = useMemo(() => toAntdTheme(mode), [mode]);
-  return (
-    <ConfigProvider theme={theme}>
-      <div
-        data-listings-skin-root
-        data-listings-skin-mode={mode}
-        style={{
-          color: token.colorText,
-          backgroundColor: token.colorBgContainer,
-          ...props.style,
-        }}
-      >
-        {props.children}
-      </div>
-    </ConfigProvider>
-  );
-}