kaafil-react-uikit 0.3.1 → 0.4.0

package/dist/{useAgencyTrip-BUYSIaC2.d.cts → useAgencyTrip-C1YmfuQq.d.cts}

@@ -1,5 +1,5 @@
 import { KaafilClient, AgencyManagersResource, TravellersResource, AgencyManagerFilters, TravellerDirectoryFilters, TripManagersResource, PartyKind, TripPartiesResource, AgencyTripsResource, AgencyTripFilters, AgencyTripSegmentCounts, TripManifestFilters, TripManifestFacets, CollectionsResource, ListEligibleCollectionsOptions, RecordCollectionOptions, OutboxOp, VoidCollectionOptions } from 'kaafil-js/client';
-import { H as CreateAgencyChecklistTemplateInput, P as PatchAgencyChecklistTemplateInput, J as RemoveAgencyChecklistTemplateInput, K as PublishAgencyChecklistTemplateInput, D as DomainHookResult } from './useVendors-DXOuZWhZ.cjs';
+import { H as CreateAgencyChecklistTemplateInput, P as PatchAgencyChecklistTemplateInput, J as RemoveAgencyChecklistTemplateInput, K as PublishAgencyChecklistTemplateInput, h as ErrorClassification, D as DomainHookResult } from './useVendors-DXOuZWhZ.cjs';
 
 type BoundAgencySettings = KaafilClient['agencies']['settings'];
 /** `AgencySettingsResponse` — never imported by name, derived off the one
@@ -107,11 +107,45 @@ interface PaginatedListFetchResult<TRow> {
 type PaginatedListFetch<TRow> = (cursor: string | undefined) => Promise<PaginatedListFetchResult<TRow>>;
 interface PaginatedListOptions {
     readonly pageSize?: number;
+    /**
+     * APPEND each forward page to the rows already held, instead of replacing
+     * them. Off by default, because an ordinary pager wants exactly one page
+     * on screen at a time.
+     *
+     * Turn it on for a caller that must hold the WHOLE list before it can
+     * render anything — grouping is the real case: a family split across a
+     * page boundary would otherwise render as two groups of two. Such a caller
+     * pages to exhaustion by calling `loadNext()` while `hasNext` holds, and
+     * without this flag it ends up with only the LAST page (and renders an
+     * empty state outright when that page lands empty on an exact page
+     * boundary). That mismatch between this hook and `ManifestResults` is the
+     * defect QA reported as "the layout breaks completely when switching to
+     * Group by".
+     *
+     * Paging backwards makes no sense while accumulating, so `hasPrev` stays
+     * false and `loadPrev()` is inert.
+     */
+    readonly accumulate?: boolean;
 }
 interface PaginatedListResult<TRow> {
     readonly rows: readonly TRow[];
     readonly hasNext: boolean;
     readonly hasPrev: boolean;
+    /**
+     * False until the first fetch has finished, whether it succeeded or
+     * failed. `rows` is `[]` both before the first response and when the list
+     * is genuinely empty, so a consumer that renders an empty state off
+     * `rows.length` alone flashes "nothing here" on every mount — which is
+     * what QA saw as the add-traveller dialog's "weird loader", once per
+     * keystroke-debounce remount. Gate the empty state on this.
+     */
+    readonly settled: boolean;
+    /**
+     * The classified failure of the most recent page fetch, or `undefined`.
+     * A failed page also clears `hasNext`, so a caller paging to exhaustion
+     * stops rather than retrying the same broken cursor forever.
+     */
+    readonly error: ErrorClassification | undefined;
     readonly loadNext: () => Promise<void>;
     readonly loadPrev: () => Promise<void>;
 }

package/dist/{useAgencyTrip-BzyJB1D9.d.ts → useAgencyTrip-gZB0NILH.d.ts}

@@ -1,5 +1,5 @@
 import { KaafilClient, AgencyManagersResource, TravellersResource, AgencyManagerFilters, TravellerDirectoryFilters, TripManagersResource, PartyKind, TripPartiesResource, AgencyTripsResource, AgencyTripFilters, AgencyTripSegmentCounts, TripManifestFilters, TripManifestFacets, CollectionsResource, ListEligibleCollectionsOptions, RecordCollectionOptions, OutboxOp, VoidCollectionOptions } from 'kaafil-js/client';
-import { H as CreateAgencyChecklistTemplateInput, P as PatchAgencyChecklistTemplateInput, J as RemoveAgencyChecklistTemplateInput, K as PublishAgencyChecklistTemplateInput, D as DomainHookResult } from './useVendors-DXOuZWhZ.js';
+import { H as CreateAgencyChecklistTemplateInput, P as PatchAgencyChecklistTemplateInput, J as RemoveAgencyChecklistTemplateInput, K as PublishAgencyChecklistTemplateInput, h as ErrorClassification, D as DomainHookResult } from './useVendors-DXOuZWhZ.js';
 
 type BoundAgencySettings = KaafilClient['agencies']['settings'];
 /** `AgencySettingsResponse` — never imported by name, derived off the one
@@ -107,11 +107,45 @@ interface PaginatedListFetchResult<TRow> {
 type PaginatedListFetch<TRow> = (cursor: string | undefined) => Promise<PaginatedListFetchResult<TRow>>;
 interface PaginatedListOptions {
     readonly pageSize?: number;
+    /**
+     * APPEND each forward page to the rows already held, instead of replacing
+     * them. Off by default, because an ordinary pager wants exactly one page
+     * on screen at a time.
+     *
+     * Turn it on for a caller that must hold the WHOLE list before it can
+     * render anything — grouping is the real case: a family split across a
+     * page boundary would otherwise render as two groups of two. Such a caller
+     * pages to exhaustion by calling `loadNext()` while `hasNext` holds, and
+     * without this flag it ends up with only the LAST page (and renders an
+     * empty state outright when that page lands empty on an exact page
+     * boundary). That mismatch between this hook and `ManifestResults` is the
+     * defect QA reported as "the layout breaks completely when switching to
+     * Group by".
+     *
+     * Paging backwards makes no sense while accumulating, so `hasPrev` stays
+     * false and `loadPrev()` is inert.
+     */
+    readonly accumulate?: boolean;
 }
 interface PaginatedListResult<TRow> {
     readonly rows: readonly TRow[];
     readonly hasNext: boolean;
     readonly hasPrev: boolean;
+    /**
+     * False until the first fetch has finished, whether it succeeded or
+     * failed. `rows` is `[]` both before the first response and when the list
+     * is genuinely empty, so a consumer that renders an empty state off
+     * `rows.length` alone flashes "nothing here" on every mount — which is
+     * what QA saw as the add-traveller dialog's "weird loader", once per
+     * keystroke-debounce remount. Gate the empty state on this.
+     */
+    readonly settled: boolean;
+    /**
+     * The classified failure of the most recent page fetch, or `undefined`.
+     * A failed page also clears `hasNext`, so a caller paging to exhaustion
+     * stops rather than retrying the same broken cursor forever.
+     */
+    readonly error: ErrorClassification | undefined;
     readonly loadNext: () => Promise<void>;
     readonly loadPrev: () => Promise<void>;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kaafil-react-uikit",
-  "version": "0.3.1",
+  "version": "0.4.0",
   "publishConfig": {
     "access": "public",
     "tag": "latest",
@@ -58,7 +58,7 @@
   "peerDependencies": {
     "react": ">=18.2.0 <20.0.0",
     "react-dom": ">=18.2.0 <20.0.0",
-    "kaafil-js": "^0.3.1"
+    "kaafil-js": "^0.4.0"
   },
   "devDependencies": {
     "react": "^19.0.0",
@@ -80,11 +80,12 @@
     "@vitest/coverage-v8": "^2.1.8"
   },
   "scripts": {
-    "build": "tsup && node scripts/build-css.mjs",
+    "build": "tsup && node scripts/build-css.mjs && node scripts/build-token-reference.mjs",
     "release": "pnpm build && pnpm publish --tag latest --no-provenance --no-git-checks",
     "release:beta": "pnpm build && pnpm publish --tag beta --no-provenance --no-git-checks",
     "build:js": "tsup",
     "build:css": "node scripts/build-css.mjs",
+    "build:tokens": "node scripts/build-token-reference.mjs",
     "typecheck": "tsc -p tsconfig.build.json --noEmit",
     "clean": "rimraf dist",
     "dev": "tsup --watch",