@abyss-project/commons-front-core 13.1.1 → 13.2.0

package/dist/components/ScanStatus/ScanStatusIndicator.d.ts

@@ -0,0 +1,102 @@
+import { default as React } from 'react';
+import { SxProps, Theme } from '@mui/material';
+/**
+ * Shared AbyssProbe scan-status indicator for every hub tool surface (board
+ * card documents, atlas documents, extract files, console ticket
+ * attachments) — the abyss-main equivalent of AbyssBeam's BeamFileScanChip
+ * (apps/front/src/features/tools/beam/components) and abyss-cloud's
+ * GalleryFileScanChip, restyled to the same AbyssProbe consumer design so a
+ * scanned file reads identically everywhere in the product.
+ *
+ * Kept decoupled from any one SDK: `@abyss-project/workspace` and
+ * `@abyss-project/console` each expose `scanStatus` typed as their own
+ * `FileScanStatus`, a structurally identical literal union to
+ * `ScanStatusValue` below (verified against both packages' published
+ * `.d.ts`), so any DTO's `scanStatus` is directly assignable here without a
+ * dependency on either SDK's runtime export (`workspace`' `FileScanStatus` is a
+ * type-only alias — it has no runtime object to import).
+ *
+ * Only two verdicts render anything:
+ * - PENDING_SCAN: "en analyse" badge/chip (warning) + rich tooltip, and the
+ *   thumbnail (where the surface shows one) renders BLURRED — see
+ *   isScanBlurred.
+ * - INFECTED: "Infecté" badge/chip (error) + rich tooltip. The thumbnail
+ *   stays SHARP: the verdict is already final, so blurring the derived
+ *   preview adds no protection — only this badge/chip needs to communicate
+ *   it (mirrors GalleryFileScanChip's isGalleryFileScanGated/
+ *   isGalleryFileScanBlurred split).
+ * CLEAN / SKIPPED / ERROR / null / undefined render nothing — a normal file.
+ *
+ * **Two visual variants (v2 refinement — "hyper compact" ask).** Default
+ * (`compact` unset) renders the full MUI `Chip` (icon + text label) — for
+ * roomy surfaces (board card modal document rows, atlas documents panel).
+ * `compact` renders an ICON-ONLY badge (no text label) for dense/tight
+ * surfaces (console attachment rows, the extract files table) where the
+ * full chip visibly overflowed/wrapped. Both variants carry the exact same
+ * rich tooltip (title + explanatory body — see `ScanStatusTooltipContent`)
+ * on hover/focus; the compact badge relies on it entirely since it drops
+ * the text label.
+ *
+ * Deliberately does not gate/disable any action (download, open, delete...)
+ * BY ITSELF: that was the superseded pre-AbyssProbe design's assumption
+ * (files were server-side locked while pending and purged once infected, so
+ * the UI had to disable dead controls). Neither assumption holds here — this
+ * component is a pure visual signal, nothing more. A DELIBERATE download/open
+ * of a PENDING or INFECTED file is instead gated by the companion
+ * `InfectedDownloadWarningModal` + `useInfectedDownloadGuard`
+ * (same directory) — a surface wraps its existing handler with the guard
+ * hook rather than this component doing anything itself. See
+ * `docs/internal/reviews/2026-07-08-storage-upload-antivirus-analysis.md`
+ * §6/§7 (D1/D8) for which hub surfaces are wired.
+ */
+export type ScanStatusValue = 'pending_scan' | 'clean' | 'infected' | 'skipped' | 'error';
+/**
+ * The 2 verdicts a deliberate download/open action is ever gated behind
+ * (see `useInfectedDownloadGuard`) — always kept a subset of
+ * `ScanStatusValue` rather than a standalone union so the two can never
+ * drift apart.
+ */
+export type ScanDownloadGatedStatus = Extract<ScanStatusValue, 'pending_scan' | 'infected'>;
+/** True only for PENDING_SCAN — the sole verdict still being analysed. */
+export declare const isScanPending: (scanStatus: ScanStatusValue | null | undefined) => boolean;
+/** True only for INFECTED — the sole verdict confirmed malicious. */
+export declare const isScanInfected: (scanStatus: ScanStatusValue | null | undefined) => boolean;
+/**
+ * True only while pending — the sole verdict whose thumbnail/preview should
+ * render BLURRED (see component doc). Always mirrors isScanPending today;
+ * kept as its own named helper (rather than reusing isScanPending at call
+ * sites) so a surface's blur decision reads intent-first, matching
+ * GalleryFileScanChip's isGalleryFileScanBlurred.
+ */
+export declare const isScanBlurred: (scanStatus: ScanStatusValue | null | undefined) => boolean;
+/**
+ * Inline blur treatment for a thumbnail/preview element mid AV-scan. Plain
+ * `CSSProperties` (not `SxProps`) so it merges into either a raw `style=`
+ * (e.g. a bare `<img>`) or an MUI `sx=` prop unchanged — the 3 surfaces with
+ * an actual image preview (board, atlas, console) render an identical blur
+ * instead of three ad-hoc filters.
+ */
+export declare const SCAN_PENDING_BLUR_STYLE: React.CSSProperties;
+export interface ScanStatusChipProps {
+    status: ScanStatusValue | null | undefined;
+    size?: 'small' | 'medium';
+    /**
+     * Icon-only badge, no text label (B) — for dense/tight surfaces (console
+     * attachment rows, the extract files table) where the full chip visibly
+     * overflowed ("badge trop long, rend très mal"). The rich tooltip (C)
+     * carries all the detail on hover/focus. Leave unset (default) on roomy
+     * surfaces (board card modal, atlas documents panel), which keep the
+     * full icon+text chip.
+     */
+    compact?: boolean;
+    sx?: SxProps<Theme>;
+}
+/**
+ * The per-file AV verdict indicator. Renders the "en analyse" (pending) or
+ * "Infecté" (infected) chip/badge with a rich tooltip; renders nothing for
+ * every other status. Always safe to render unconditionally — callers don't
+ * need to guard with isScanPending/isScanInfected first (mirrors
+ * BeamFileScanChip).
+ */
+export declare const ScanStatusChip: React.FC<ScanStatusChipProps>;
+export default ScanStatusChip;

package/dist/components/ScanStatus/ScanStatusIndicator.spec.d.ts

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

package/dist/components/ScanStatus/index.d.ts

@@ -0,0 +1,6 @@
+export { ScanStatusChip, SCAN_PENDING_BLUR_STYLE, isScanBlurred, isScanInfected, isScanPending, } from './ScanStatusIndicator';
+export type { ScanDownloadGatedStatus, ScanStatusChipProps, ScanStatusValue, } from './ScanStatusIndicator';
+export { InfectedDownloadWarningModal } from './InfectedDownloadWarningModal';
+export type { InfectedDownloadWarningModalProps } from './InfectedDownloadWarningModal';
+export { useInfectedDownloadGuard } from './use-infected-download-guard.hook';
+export type { UseInfectedDownloadGuardResult } from './use-infected-download-guard.hook';

package/dist/components/ScanStatus/use-infected-download-guard.hook.d.ts

@@ -0,0 +1,37 @@
+import { default as React } from 'react';
+import { ScanStatusValue } from './ScanStatusIndicator';
+export interface UseInfectedDownloadGuardResult {
+    /**
+     * Wrap a download/open action with the scan-status download policy (A):
+     * when `scanStatus` is INFECTED or PENDING_SCAN, defers `action` behind
+     * the warning modal (resolved only once the user retypes the confirm
+     * phrase, with status-appropriate copy/color); for every other status —
+     * clean/skipped/error/null/undefined — `action` runs immediately,
+     * unchanged. An authenticated owner is allowed to deliberately download
+     * BOTH a still-analysing and a confirmed-infected file, each behind the
+     * same type-to-confirm gate — only the warning text differs.
+     */
+    guardDownload: (scanStatus: ScanStatusValue | null | undefined, fileName: string, action: () => void | Promise<void>) => void;
+    /** Render this once per surface (anywhere in the tree — it's a portal-based
+     * dialog), alongside the surface's other modals. */
+    infectedDownloadModal: React.ReactNode;
+}
+/**
+ * Companion hook for `InfectedDownloadWarningModal` — see that file for the
+ * policy this implements. Keeps the "is this download gated, and by which
+ * verdict?" branch and the modal's open/pending state in one place so a hub
+ * surface only has to wrap its existing handler, e.g.:
+ *
+ * ```tsx
+ * const { guardDownload, infectedDownloadModal } = useInfectedDownloadGuard();
+ * // ...
+ * <IconButton onClick={() =>
+ *   guardDownload(document.scanStatus, document.name, () => handleDownload(document))
+ * }>
+ *   <Download />
+ * </IconButton>
+ * // ...
+ * {infectedDownloadModal}
+ * ```
+ */
+export declare const useInfectedDownloadGuard: () => UseInfectedDownloadGuardResult;

package/dist/components/ScanStatus/use-infected-download-guard.hook.spec.d.ts

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

package/dist/components/data/DataTable/data-table.types.d.ts

@@ -23,6 +23,11 @@ export interface DataColumn<T> {
     text?(row: T): string;
     /** Column width (`120`, `'20%'`); the columns without one share the rest. */
     width?: number | string;
+    /**
+     * For a column without `width`, in px: the narrowest it is laid out. When the columns shown do
+     * not fit with it, the table keeps it and scrolls sideways in its frame.
+     */
+    minWidth?: number;
     align?: ColumnAlign;
     sortable?: boolean;
     /** Sets the cells in the mono family (amounts, identifiers, dates). */

package/dist/components/index.d.ts

@@ -6,3 +6,4 @@ export * from './meaning';
 export * from './mobile';
 export * from './states';
 export * from './structure';
+export * from './ScanStatus';

package/dist/components/inputs/ExpressionSearch/expression-fade.d.ts

@@ -0,0 +1,6 @@
+/**
+ * The mask over the edges of the expression field that hide a part of a long expression: the text
+ * runs on past a faded edge, and scrolls into view. `width` is the length of each fade; the mask
+ * only reads the alpha of its colours.
+ */
+export declare const fadeMask: (start: boolean, end: boolean, width: string) => string;

package/dist/cookie-consent.js

@@ -1,19 +1,20 @@
-import { A as e, c as a, C as n, D as C, R as i, V as t, d as r, f as A, r as k, e as c, u as l, b, a as f, w as u } from "./AbyssCookieConsentProvider-DJTKl58k.js";
-import { C as E } from "./CookieConsentSettings.component-ZF6umBSH.js";
+import { A as s, c as a, C as n, D as C, R as i, V as t, d as r, r as A, e as k, u as c, b as l, a as f, w as b } from "./AbyssCookieConsentProvider-Ds99df0E.js";
+import { C as u } from "./CookieConsentSettings.component-DoWLHqw5.js";
+import { f as E } from "./use-rich-intl.hook-BETUyCkW.js";
 export {
-  e as AbyssCookieConsentProvider,
+  s as AbyssCookieConsentProvider,
   a as COOKIE_NAME,
   n as CookieConsentBanner,
-  E as CookieConsentSettings,
+  u as CookieConsentSettings,
   C as DEFAULT_PRIVACY_HREF,
   i as ReconcileAction,
   t as VALIDITY_DAYS,
   r as clearCookie,
-  A as flattenTranslations,
-  k as readCookie,
-  c as reconcile,
-  l as useAbyssCookieConsent,
-  b as useCookieConsent,
+  E as flattenTranslations,
+  A as readCookie,
+  k as reconcile,
+  c as useAbyssCookieConsent,
+  l as useCookieConsent,
   f as useOptionalAbyssCookieConsent,
-  u as writeCookie
+  b as writeCookie
 };