@factorialco/f0-react 2.60.0 → 2.61.1

package/dist/ai.d.ts

@@ -4702,6 +4702,11 @@ declare module "gridstack" {
 }
 
 
+declare namespace Calendar {
+    var displayName: string;
+}
+
+
 declare module "@tiptap/core" {
     interface Commands<ReturnType> {
         aiBlock: {
@@ -4751,11 +4756,6 @@ declare module "@tiptap/core" {
 }
 
 
-declare namespace Calendar {
-    var displayName: string;
-}
-
-
 declare namespace F0GraphNodeWrapperInner {
     var displayName: string;
 }

package/dist/ai.js

@@ -1,6 +1,6 @@
-import { D as e, F as r, a as t, e as o, f as i, c as n, d as F, I as C, P as A, b as l, u as d } from "./F0CanvasPanel-Dwn0nUXM.js";
+import { D as e, F as r, a as t, e as o, f as i, c as n, d as F, I as C, P as A, b as l, u as d } from "./F0CanvasPanel-mGgQF8IR.js";
 import { defaultTranslations as m } from "./i18n-provider-defaults.js";
-import { A as c, C as I, h as P, t as v, v as f, x as p, n as T, j as g, r as y, y as S, q as x, s as H, k as V, e as b, g as k, l as w, F as M, i as O, a as D, p as j, m as q, o as z, b as B, f as E, w as L, c as R, d as G, u as J } from "./useChatHistory-t42cvE76.js";
+import { A as c, C as I, h as P, t as v, v as f, x as p, n as T, j as g, r as y, y as S, q as x, s as H, k as V, e as b, g as k, l as w, F as M, i as O, a as D, p as j, m as q, o as z, b as B, f as E, w as L, c as R, d as G, u as J } from "./useChatHistory-B3Rzija0.js";
 export {
   c as AiChatTranslationsProvider,
   I as ChatSpinner,

package/dist/experimental.d.ts

@@ -1124,7 +1124,73 @@ declare type BreadcrumbBaseItemType = NavigationItem & {
     label: string;
 };
 
-export declare type BreadcrumbItemType = BreadcrumbLoadingItemType | BreadcrumbNavItemType | BreadcrumbSelectItemType;
+/**
+ * A breadcrumb "jump-to" select bound to a OneDataCollection: the options are
+ * fetched from the declared `source`, seeded with the filters/sortings the
+ * list persisted under `collectionId` — so on the detail page (even via a
+ * direct link, with the list never mounted) the select only shows the items
+ * the user was looking at on the list.
+ *
+ * F0 owns the seeding, pagination handling (a `pages` adapter is transparently
+ * consumed as infinite scroll), current selection, navigation, and
+ * loop-safety: `source` is captured when the crumb mounts, so inline-recreated
+ * item objects never retrigger fetches. Give the item a new `id` to swap
+ * sources.
+ */
+export declare type BreadcrumbCollectionSelectItemType = BreadcrumbBaseItemType & {
+    type: "collection-select";
+    /**
+     * The `id` of the OneDataCollection whose persisted state seeds the source
+     * (WITHOUT the `datacollection-` prefix). Empty/missing storage → the
+     * source is used unfiltered.
+     */
+    collectionId: string;
+    /** The declared data source — no mounted collection needed. */
+    source: DataSourceDefinition<RecordType, FiltersDefinition, SortingsDefinition, GroupingDefinition<RecordType>>;
+    mapOptions: (item: RecordType) => F0SelectItemProps<string, RecordType>;
+    /** Current item id (the record the detail page is showing). */
+    value?: string;
+    /**
+     * Fallback option so a direct link shows the current item as selected
+     * before/without it appearing in the fetched options. The item `label` is
+     * used as the trigger label until an option is selected.
+     */
+    defaultItem?: F0SelectItemObject<string, RecordType>;
+    searchbox?: boolean;
+    /** Which persisted state to seed. @default { filters: true, sortings: true } */
+    seed?: {
+        filters?: boolean;
+        sortings?: boolean;
+    };
+    /**
+     * Render the source's filter definitions as an editable filter picker
+     * inside the dropdown, pre-applied with the seeded persisted filters —
+     * letting users refine the jump-to list in place. When false the seeded
+     * filters are still applied, just not editable.
+     * @default false
+     */
+    showFilters?: boolean;
+    /**
+     * Called when the user edits the in-dropdown filters (`showFilters`).
+     * Feed the value to `useDataCollectionItemNavigation`'s `currentFilters`
+     * so the detail-page prev/next arrows and counter follow the same refined
+     * context the dropdown is showing.
+     */
+    onFiltersChange?: (filters: FiltersState<FiltersDefinition>) => void;
+} & ({
+    /**
+     * Href to navigate to when an option is picked, routed through the
+     * app's LinkProvider. Return undefined to skip navigation.
+     */
+    getItemHref: (value: string, item?: RecordType) => string | undefined;
+    onSelect?: (value: string, item?: RecordType) => void;
+} | {
+    getItemHref?: never;
+    /** Imperative escape hatch (e.g. router.push) when hrefs don't fit. */
+    onSelect: (value: string, item?: RecordType) => void;
+});
+
+export declare type BreadcrumbItemType = BreadcrumbLoadingItemType | BreadcrumbNavItemType | BreadcrumbSelectItemType | BreadcrumbCollectionSelectItemType;
 
 export declare type BreadcrumbLoadingItemType = Pick<BreadcrumbBaseItemType, "id"> & {
     loading: true;
@@ -4596,6 +4662,12 @@ declare type F0SelectBaseProps<T extends string, R = unknown> = {
     onSearchChange?: (value: string) => void;
     searchValue?: string;
     onOpenChange?: (open: boolean) => void;
+    /**
+     * Called when the user changes the in-dropdown filters (requires a `source`
+     * with filter definitions). Lets consumers keep an external context — e.g.
+     * detail-page navigation — in sync with what the dropdown is showing.
+     */
+    onFiltersChange?: (filters: FiltersState<FiltersDefinition>) => void;
     searchEmptyMessage?: string;
     className?: string;
     actions?: Action[];
@@ -8487,6 +8559,13 @@ declare type UseDataCollectionDataReturn<R extends RecordType> = UseDataReturn<R
  * `currentSortings`: the definition values apply on mount and the hydrated
  * state lands right after, mirroring what the user last saw on the list.
  *
+ * When the adapter implements the optional id-relative `fetchItemNeighbors`
+ * capability, gaps the loaded window can't answer (deep direct link to an
+ * item beyond the first page, or a neighbor past the window edge) are
+ * resolved backend-side under the same filters/sortings/search — prev/next
+ * and the counter then behave as if the whole filtered set were loaded.
+ * Without the capability, behavior is window-only as before.
+ *
  * @example
  * ```tsx
  * const { navigation } = useDataCollectionItemNavigation({
@@ -8543,6 +8622,14 @@ export declare interface UseDataCollectionItemNavigationProps<R extends RecordTy
      * @default true
      */
     restorePersistedState?: boolean;
+    /**
+     * Controlled filters for the navigation context — wins over the persisted
+     * list filters. Feed it the filters the user refined elsewhere (e.g. a
+     * collection-bound breadcrumb select's `onFiltersChange`) so prev/next and
+     * the counter follow that same context. Changing it refetches and
+     * re-resolves neighbors; `undefined` keeps the persisted/definition state.
+     */
+    currentFilters?: FiltersState<Filters>;
     /**
      * Forwarded to `useDataCollectionSource` for `dataAdapter` memoization,
      * same convention as `useDataCollectionSource(source, deps)`.
@@ -9168,6 +9255,11 @@ declare module "gridstack" {
 }
 
 
+declare namespace Calendar {
+    var displayName: string;
+}
+
+
 declare module "@tiptap/core" {
     interface Commands<ReturnType> {
         aiBlock: {
@@ -9217,11 +9309,6 @@ declare module "@tiptap/core" {
 }
 
 
-declare namespace Calendar {
-    var displayName: string;
-}
-
-
 declare namespace F0GraphNodeWrapperInner {
     var displayName: string;
 }