@declarion/react 0.43.0 → 0.45.0

package/dist-lib/components/pages/exportRequest.d.ts

@@ -1,9 +1,9 @@
-import type { FilterNodeParam } from "../../types/api";
+import type { FilterNode } from "../../lib/filters";
 /** ExportQuery mirrors the Go ExportQuery struct (server/handlers/data_export.go).
  *  Field order matches; semantics match parseListParams 1:1. */
 export interface ExportQuery {
     screen?: string;
-    filters?: FilterNodeParam[];
+    filters?: FilterNode[];
     search?: string;
     sort?: string;
     include_deleted?: boolean;
@@ -34,7 +34,7 @@ export interface ListViewState {
     /** Active screen code, when the list is rendered through a screen. */
     screenCode?: string;
     /** JSON filter tree (the same shape sent in the `filters` URL param). */
-    jsonFilters?: FilterNodeParam[];
+    jsonFilters?: FilterNode[];
     /** Debounced search value from the toolbar. */
     search?: string;
     /** "field:asc" / "field:desc" sort spec. */

package/dist-lib/components/pages/list/filter-meta.d.ts

@@ -1,10 +1,24 @@
-import type { Entity, ScreenFilterSpecialValues } from "../../../types/schema";
+import type { Entity, Screen, ScreenFilterSpecialValues } from "../../../types/schema";
 import type { FilterFieldMeta } from "../../../components/filters/FilterDrawer";
-import type { FilterOp } from "../../../lib/filters";
-/** Build FilterFieldMeta array from screen + entity for the FilterDrawer. */
-export declare function buildFilterFieldMeta(screen: {
-    filters?: string[];
+/**
+ * Build FilterFieldMeta array from screen + entity for the FilterDrawer.
+ *
+ * The per-type operator lists come from the server (`screen.filter_operators`),
+ * never from a table here. The client used to keep its own map and it had
+ * already diverged: array, multilang, json and bytes fields fell through to
+ * `["eq","not_eq","is_empty","is_not_empty"]`, offering two operators the query
+ * builder rejects and hiding `contains`, the one that works. The server owns
+ * the field-type -> operator mapping because the server is what enforces it.
+ *
+ * A field the server published no operators for is OMITTED rather than given a
+ * guessed list: an operator the builder rejects is worse than an absent field,
+ * because the user only finds out after building the filter.
+ *
+ * Which fields appear at all is SCREEN-SCOPED - `screen.filters` when declared,
+ * every entity field otherwise. That is a UI affordance, not an access control:
+ * the server applies no screen scoping to caller filters.
+ */
+export declare function buildFilterFieldMeta(screen: (Pick<Screen, "filters"> & {
     filter_special_values?: Record<string, ScreenFilterSpecialValues>;
-} | undefined, entity: Pick<Entity, "fields" | "status_groups" | "properties"> | undefined, entities?: Record<string, Entity>): FilterFieldMeta[];
-/** Map field type to available filter operators. */
-export declare function fieldTypeToOperators(type: string): FilterOp[];
+    filter_operators?: Record<string, string[]>;
+}) | undefined, entity: Pick<Entity, "fields" | "status_groups" | "properties"> | undefined, entities?: Record<string, Entity>): FilterFieldMeta[];

package/dist-lib/hooks/useCursorEntityData.d.ts

@@ -1,5 +1,6 @@
 import { type QueryKey } from "@tanstack/react-query";
-import type { FilterNodeParam, Refs, V2Meta } from "../types/api";
+import type { Refs, V2Meta } from "../types/api";
+import type { FilterNode } from "../lib/filters";
 /**
  * Query-key root for the cursor (infinite) entity list. Distinct from the
  * offset list's `"entity-data"` so the SSE handler can RESET it (drop pages,
@@ -22,7 +23,7 @@ export declare function cursorEntityStableKey(params: CursorEntityDataParams): s
 export declare function cursorEntityDataQueryKey(entity: string | undefined, params: CursorEntityDataParams): QueryKey;
 export interface CursorEntityDataParams {
     sort?: string;
-    filters?: FilterNodeParam[];
+    filters?: FilterNode[];
     search?: string;
     select?: string[];
     expand?: string[];