@propriety/court-calendar 1.0.158 → 1.0.159

package/dist/__tests__/ModalActionsSaveGuard.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/__tests__/hooks/UseGuardedAction.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/_components/Modal/DateDetails/PortalFab.d.ts

@@ -1,9 +1,11 @@
 import { ReactNode } from 'react';
-export default function PortalFab({ in: visible, tooltip, icon, onClick, badgeContent, containerId, bottom, right, color, }: {
+export default function PortalFab({ in: visible, tooltip, icon, onClick, disabled, badgeContent, containerId, bottom, right, color, }: {
     in: boolean;
     tooltip: string;
     icon: ReactNode;
     onClick: (e: React.MouseEvent<HTMLElement>) => void;
+    /** Blocks the FAB while its action is running — a Fab is clickable for as long as it is visible. */
+    disabled?: boolean;
     badgeContent?: number;
     containerId?: string;
     bottom?: number;

package/dist/_components/Modal/Layout/ModalActions.d.ts

@@ -1,8 +1,8 @@
 import { ModalMode } from '../types';
 export default function ModalActions({ modalMode, onDelete, onSave, setModalMode, setIsOpen, isAdmin, createdBy, createdOn, }: {
     modalMode: ModalMode;
-    onDelete: () => void;
-    onSave: () => void;
+    onDelete: () => void | Promise<unknown>;
+    onSave: () => void | Promise<unknown>;
     setModalMode: (mode: ModalMode) => void;
     setIsOpen: (isOpen: boolean) => void;
     isAdmin: boolean;

package/dist/hooks/UseGuardedAction.d.ts

@@ -0,0 +1,22 @@
+/**
+ * Wraps an async action so a second click cannot start it while the first is still running.
+ *
+ * Every mutating button in this app is a multi-second round trip with no feedback of its own,
+ * which makes clicking again the natural response to "nothing happened". Creating a court date
+ * that way sent a second POST for the same date, and the server — whose duplicate check could
+ * not see a date it had not committed yet — inserted it again and answered 500, over a date
+ * that had in fact been created correctly.
+ *
+ * The guarantee is the ref, not `busy`: two clicks can land before React re-renders with the
+ * new state, and both would read `busy === false`. `busy` exists only to drive the button's
+ * disabled state and label. Deliberately no `useCallback` — the ref persists across renders
+ * whatever `run`'s identity is, so a stable identity would buy nothing.
+ *
+ * An action that throws is reported rather than left as an unhandled rejection: these run from
+ * click handlers, which have nowhere to propagate to but the console.
+ *
+ * @param action     The work to run. Its promise is awaited, so the guard covers the whole call.
+ * @param operation  What the user was trying to do, for the error report ("Delete court date").
+ * @returns `[busy, run]` — `busy` for `disabled`/label, `run` for `onClick`.
+ */
+export declare function useGuardedAction(action: () => void | Promise<unknown>, operation: string): [boolean, () => Promise<void>];