@declarion/react 0.51.0 → 0.53.0

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

@@ -15,7 +15,7 @@ export interface DocumentsMenuProps {
     /** True when the caller can manage tenant document templates (heuristic:
      *  `document_template` is present & readable in `schema.entities`). Gates
      *  the lazy `document.templates.available` visibility probe so a
-     *  template-less, non-manager caller (the Haia default) makes ZERO extra
+     *  template-less, non-manager caller - the default - makes ZERO extra
      *  network calls - Business Case 6. */
     canManageTemplates?: boolean;
 }

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

@@ -9,11 +9,11 @@ interface RecordDocumentsPanelProps {
      *  false/absent the shelf mounts ONLY if the record already has >=1
      *  attached document - it never orphans visible history, but it also
      *  never shows an empty "no documents" shelf on an entity with nothing to
-     *  generate and nothing generated (the Haia case). */
+     *  generate and nothing generated. */
     canGenerateOne?: boolean;
     /** True when the caller can manage tenant document templates. Together with
      *  canGenerateOne this gates whether the attachment fetch runs at all: a
-     *  template-less, non-manager caller (the Haia default) makes ZERO
+     *  template-less, non-manager caller - the default - makes ZERO
      *  document.object_links calls per record view. The rare orphaned-attachment
      *  case (a template was removed but its current-attached docs remain) then
      *  surfaces only to managers on the record and to everyone via My Documents,

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

@@ -39,7 +39,12 @@ export interface ListQueryResult {
     error: unknown;
     /** True while a load has been running long enough to be worth saying so. */
     isLoadingStale: boolean;
-    retry: () => void;
+    /**
+     * Cancels this query's in-flight fetch and refetches it, resolving when both
+     * have settled - in that order. Returning nothing made every completion-based
+     * state silently instant, so a control that waited on it never waited.
+     */
+    retry: () => Promise<void>;
     /** The total, and how it was produced. Undefined while the count is in flight
      *  or after it failed - a caller degrades to the loaded row count. */
     countTotal: number | undefined;

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

@@ -9,10 +9,16 @@
  */
 export interface RefreshControlProps {
     liveObject: {
+        /** Resolves when the refresh it starts has settled. See useOwnRefresh. */
         refetch: () => unknown;
-        isFetching: boolean;
         isLoading: boolean;
         isLive: boolean;
+        /**
+         * @deprecated Ignored; the control reports only the refresh a person
+         * started. Passing it changes nothing. Declared so a consumer that builds
+         * this object literally still compiles.
+         */
+        isFetching?: boolean;
     };
     realtime?: boolean;
 }

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

@@ -0,0 +1,9 @@
+/**
+ * Whether the refresh THIS control started is still running. A control driven
+ * by its query's flag reports somebody else's work and sits disabled exactly
+ * when a person reaches for it. docs/architecture.md.
+ */
+export declare function useOwnRefresh(refetch: () => unknown): {
+    refreshing: boolean;
+    refresh: () => void;
+};