@declarion/react 0.48.2 → 0.49.0

package/dist-lib/components/pages/list/useListViews.d.ts

@@ -0,0 +1,46 @@
+import type { FilterNode } from "../../../lib/filters";
+import { type Screen } from "../../../types/schema";
+import type { ViewItem } from "../../../components/list/ViewSwitcher";
+interface ListViewsInput {
+    screenCode: string;
+    screen: Screen | undefined;
+    searchParams: URLSearchParams;
+    setSearchParams: (next: URLSearchParams, options?: {
+        replace?: boolean;
+    }) => void;
+    userId: string | undefined;
+    tenantId: string | undefined;
+    /** A malformed `?filters=` bookmark. A visible recoverable state must not be
+     *  replaced by a personal default view before the user can see it. */
+    filterError: boolean;
+    /** The live layout, compared against the saved one to decide dirtiness and
+     *  written into a save. */
+    filters: FilterNode[];
+    visibleColumns: string[];
+    sort: string | undefined;
+}
+/** Which saved view a list screen is showing, and every way that changes. */
+export interface ListViews {
+    all: ViewItem[];
+    activeId: string | null;
+    active: ViewItem | undefined;
+    /** True when the live layout differs from what the active view saved. */
+    isDirty: boolean;
+    /** Open a view, or clear to no view. Also the reset gesture: open the same
+     *  view again. */
+    apply: (view: ViewItem) => void;
+    saveAsNew: (name: string) => Promise<void>;
+    overwriteActive: () => Promise<void>;
+    isSaving: boolean;
+}
+/**
+ * The saved views a list screen offers.
+ *
+ * A view owns the LOGICAL layout - filters, columns, sort - and nothing else.
+ * Column widths are per device and never travel in one.
+ */
+export declare function useListViews({ screenCode, screen, searchParams, setSearchParams, userId, tenantId, filterError, filters, visibleColumns, sort, }: ListViewsInput): ListViews;
+/** The name a save dialog offers to overwrite, or null when the active view is
+ *  not the caller's to overwrite. */
+export declare function overwritableViewName(active: ViewItem | undefined): string | null;
+export {};

package/dist-lib/components/pages/list/useRowMenu.d.ts

@@ -1,5 +1,5 @@
 import { type ResolvedActionLayoutNode } from "../../../lib/actions";
-import type { ActionRunHandler, WidgetContext } from "../../../components/shared/ResponsiveActionBar";
+import type { ActionRunHandler, WidgetContext } from "../../../components/actions/ResponsiveActionBar";
 import type { Action, Entity, Screen } from "../../../types/schema";
 export interface UseRowMenuArgs {
     row: Record<string, unknown>;

package/dist-lib/components/shared/RefreshControl.d.ts

@@ -1,6 +1,19 @@
-import type { LiveObjectResult } from "../../hooks/useLiveObject";
-export interface RefreshControlProps<T extends Record<string, unknown> = Record<string, unknown>> {
-    liveObject: Pick<LiveObjectResult<T>, "refetch" | "isFetching" | "isLoading" | "isLive">;
+/**
+ * What the control needs, which is less than any one caller happens to have.
+ *
+ * A detail page hands it a `useLiveObject` result; a list hands it a refresh
+ * that cancels in-flight queries first and returns nothing. Typing `refetch` as
+ * react-query's own signature would have made the second caller impossible and
+ * left the list with a copy of this component - which is how the two surfaces
+ * drifted in the first place.
+ */
+export interface RefreshControlProps {
+    liveObject: {
+        refetch: () => unknown;
+        isFetching: boolean;
+        isLoading: boolean;
+        isLive: boolean;
+    };
     realtime?: boolean;
 }
-export declare function RefreshControl<T extends Record<string, unknown> = Record<string, unknown>>({ liveObject, realtime, }: RefreshControlProps<T>): import("react").JSX.Element;
+export declare function RefreshControl({ liveObject, realtime }: RefreshControlProps): import("react").JSX.Element;