@sequenceholdings/atlas-ui 0.3.2 → 1.0.1

package/dist/index.d.ts

@@ -1506,68 +1506,13 @@ export declare interface FilterOption<T extends string> {
     swatch?: ReactNode;
 }
 
-export declare function FilterPill({ label, options, selected, onChange }: FilterPillProps): JSX.Element | null;
-
-/**
- * @deprecated Do not use in new code, and migrate existing usages off it.
- * `FilterPill` is being retired from the design system: filtering must go
- * through the canonical support — `ProDataTable`'s native filter funnel
- * (`meta.filter` → `FilterMenu`), which owns state, ordering (search always
- * before filter), and DS-composed controls. This standalone pill is removed
- * from the design-system gallery; it is still exported from
- * `@sequenceholdings/atlas-ui` (deprecated) purely so existing consumers keep
- * compiling — kept only until the remaining app consumers (chat / crm /
- * permissions / groups / jarvis / billing) are migrated to the funnel, after
- * which the exports and this file go away (DES-126).
- *
- * FilterPill — a compact multi-select filter anchored to a table toolbar.
- *
- * Visual contract mirrors `SelectTrigger` so a toolbar of FilterPills +
- * SearchInput + Select reads as one coherent row of controls, not a
- * grab-bag of visual treatments:
- *
- *   - Height:        h-9 (36px)
- *   - Radius:        `rounded-control` — operable and one line tall
- *   - Border/bg:     `border bg-card` — `--input` border, raised surface,
- *                    same palette as Select/Input. NOT `background`: that is
- *                    the PAGE role (ds-neutral-50 under v2, not white), which
- *                    rendered the pill as a grey chip next to the white
- *                    outline controls beside it. `Button variant="outline"`
- *                    carries the same note and the same `dark:bg-input/30`
- *                    lift, since in dark the resting fill matches the darkest
- *                    surface and vanishes.
- *   - Padding:       px-3 py-1
- *   - Text:          text-base md:text-sm (14px on desktop)
- *   - Focus ring:    focus:ring-1 focus:ring-ring (keyboard-visible)
- *
- * Rationale for NOT using `rounded-full` + primary fill (the old shape):
- *   1. Visual noise. When a toolbar mixes a SearchInput (8px radius),
- *      two FilterPills (full radius), and a Select (8px radius), the
- *      eye has to re-parse each control. A consistent radius reads as
- *      one group.
- *   2. Active state hierarchy. A solid primary-colored pill made the
- *      active filter feel like a CTA. Filters are not CTAs — the
- *      primary action on a dashboard is "run query" / "save", not
- *      "I've narrowed my view". A subtle count chip communicates
- *      activity without competing with real buttons.
- *
- * Active state now uses a tiny pill-shaped count badge next to the
- * label. The trigger itself stays in the Select-aligned neutral look.
- */
-declare interface FilterPillProps {
-    label: string;
-    options: string[];
-    selected: string[];
-    onChange: (values: string[]) => void;
-}
-
 /**
  * @deprecated Do not use in new code, and migrate existing usages off it.
  * `FilterSelect` is retired in favor of `MultiSelect` (searchable cmdk list,
  * always-visible checkboxes, stacked trigger icons). It is still exported from
  * `@sequenceholdings/atlas-ui` (deprecated) so remaining consumers keep
- * compiling — remove only after the blast-radius scan is clean (FilterPill /
- * DES-261 deprecate-before-delete pattern).
+ * compiling — remove only after the blast-radius scan is clean (DES-261
+ * deprecate-before-delete pattern).
  *
  * A compact multi-select filter for a table/list toolbar: a trigger with a count
  * chip when active, and a popover of swatch + label rows with a check on the
@@ -1933,7 +1878,7 @@ declare interface MetricGridProps {
     className?: string;
 }
 
-export declare function MultiSelect({ label, countLabel, options, selected, onChange, searchPlaceholder, emptyMessage, maxStackedIcons, hideWhenEmpty, className, }: MultiSelectProps): JSX.Element | null;
+export declare function MultiSelect({ label, countLabel, options, selected, onChange, searchPlaceholder, emptyMessage, maxStackedIcons, hideWhenEmpty, modal, className, }: MultiSelectProps): JSX.Element | null;
 
 /**
  * Fields shared by `MultiSelect` (trigger + popover) and the standalone
@@ -2050,6 +1995,27 @@ declare interface MultiSelectProps extends MultiSelectCoreProps {
      * that hasn't loaded yet).
      */
     hideWhenEmpty?: boolean;
+    /**
+     * Render the popover as a modal layer. Pass `true` when the MultiSelect
+     * lives inside a Dialog.
+     *
+     * A Dialog scroll-locks the page with react-remove-scroll, allowing wheel
+     * events only within the dialog's own content subtree. This popover portals
+     * to the body, so it sits outside that subtree and the lock swallows every
+     * wheel event over the option list — the list is a real scroll container
+     * (`max-h-[300px] overflow-y-auto`) but cannot be scrolled, stranding every
+     * option past the ~7th. Radix `Select` is unaffected because it implements
+     * its own scrolling rather than relying on native overflow.
+     *
+     * Modal mode gives the popover its own scroll lock. react-remove-scroll
+     * keeps a stack of locks with only the innermost active, so the popover's
+     * lock supersedes the dialog's and allows wheel within the popover.
+     *
+     * Defaults to `false` because modal mode also traps focus and blocks outside
+     * pointer events — in a filter toolbar that breaks clicking straight from one
+     * open facet to the next, which is the dominant use of this component.
+     */
+    modal?: boolean;
     className?: string;
 }