react-semaphor 0.1.510 → 0.1.512

package/dist/types/components/error-fallbacks/render-reset-error-boundary.d.ts

@@ -0,0 +1,33 @@
+import { Component, ReactNode } from 'react';
+import { FallbackProps } from 'react-error-boundary';
+type RenderResetErrorBoundaryProps = {
+    /** The boundary retries its children whenever any of these change. */
+    resetKeys: readonly unknown[];
+    fallbackRender: (props: FallbackProps) => ReactNode;
+    children?: ReactNode;
+};
+type RenderResetErrorBoundaryState = {
+    hasError: boolean;
+    error: unknown;
+    /** `resetKeys` as they were when the error was caught. */
+    errorKeys: readonly unknown[] | null;
+};
+/**
+ * Error boundary whose `resetKeys` check runs during render.
+ *
+ * `react-error-boundary` compares `resetKeys` in `componentDidUpdate`. The
+ * dashboard stays mounted under `<Activity mode="hidden">` while the visual
+ * editor is open, and hidden trees re-render without running update
+ * lifecycles; on reveal they run `componentDidMount` instead. A repair made
+ * in the editor therefore never reset a failed card, which stayed on its
+ * error state after Accept. `getDerivedStateFromProps` runs on every render,
+ * hidden or not, so this boundary sees the change.
+ */
+export declare class RenderResetErrorBoundary extends Component<RenderResetErrorBoundaryProps, RenderResetErrorBoundaryState> {
+    state: RenderResetErrorBoundaryState;
+    static getDerivedStateFromError(error: unknown): Partial<RenderResetErrorBoundaryState>;
+    static getDerivedStateFromProps(props: RenderResetErrorBoundaryProps, state: RenderResetErrorBoundaryState): Partial<RenderResetErrorBoundaryState> | null;
+    private resetErrorBoundary;
+    render(): ReactNode;
+}
+export {};

package/dist/types/components/visual/data-table/hooks/use-data-table-logic.d.ts

@@ -84,6 +84,11 @@ export declare function useDataTableLogic(props: DataTableLogicProps): {
     totalRows: number;
     isTablePrintDisplayMode: boolean;
     onSortChange: ((sorting: SortingState) => void) | undefined;
+    pagination: {
+        pageIndex: number;
+        pageSize: number;
+    };
+    handlePaginationChange: (updater: import('@tanstack/table-core').PaginationState | ((old: import('@tanstack/table-core').PaginationState) => import('@tanstack/table-core').PaginationState)) => void;
     paginationMode: import('../utils/pagination-utils.js').PaginationMode;
     paginationMetadata: any;
     contextTimezone: string | undefined;

package/dist/types/lib/dashboard/open-card-in-visual-editor.d.ts

@@ -0,0 +1,15 @@
+import { useManagementStore } from '../stores/management-store.js';
+import { TCard, TFrame } from '../types/common-types.js';
+type ManagementState = ReturnType<typeof useManagementStore.getState>;
+/** Saved-dashboard edit permission, as the dashboard runtime reads it. */
+export declare function selectCanEditDashboard(state: ManagementState): boolean;
+/**
+ * Opens the visual editor on one dashboard card from any dashboard state,
+ * including view mode. Store values are read at call time, so callers such as
+ * error fallbacks don't subscribe to dashboard or editor state to offer it.
+ */
+export declare function openCardInVisualEditor({ frame, card, }: {
+    frame: TFrame;
+    card: TCard;
+}): void;
+export {};

package/dist/types/lib/dashboard-pagination/dashboard-card-pagination.d.ts

@@ -1,4 +1,4 @@
-import { PaginationConfig } from '../types/explorer-types.js';
+import { PaginationConfig, PaginationMetadata } from '../types/explorer-types.js';
 export type DashboardCardPaginationState = PaginationConfig & {
     queryInputIdentity: string;
 };
@@ -14,4 +14,11 @@ type ResolveDashboardCardPaginationParams = {
  */
 export declare function resolveDashboardCardPagination({ current, defaultPageSize, queryInputIdentity, }: ResolveDashboardCardPaginationParams): PaginationConfig;
 export declare function dashboardCardPaginationMatches(current: DashboardCardPaginationState | undefined, pagination: PaginationConfig, queryInputIdentity: string): boolean;
+/**
+ * Keeps pagination chrome aligned with the request being rendered while React
+ * Query retains the previous response. Counts and navigation capability remain
+ * useful placeholders, but the displayed page must belong to the current query
+ * input identity.
+ */
+export declare function resolveDashboardPaginationMetadata(metadata: PaginationMetadata | undefined, effectivePagination: PaginationConfig | undefined): PaginationMetadata | undefined;
 export {};

package/package.json

@@ -5,7 +5,7 @@
     "email": "support@semaphor.cloud"
   },
   "license": "MIT",
-  "version": "0.1.510",
+  "version": "0.1.512",
   "description": "Fully interactive and customizable dashboards for your apps.",
   "keywords": [
     "react",