@flamingo-stack/openframe-frontend-core 0.0.577 → 0.0.578

package/dist/components/chat/utils/nav-click-handler.d.ts

@@ -1,24 +0,0 @@
-/**
- * Click router for chat-rendered nav links — chip block, `<ChatCardNavWrap>`,
- * `<NavLinkAnchorViaRuntime>`.
- *
- * @deprecated Thin wrapper around the unified `executeNavigation` primitive
- * (`execute-navigation.ts`). Kept so the existing chat callers' call shape
- * (`handleChatNavClick(e, runtime, {href,path,targetPlatform}, fallbackNavigate)`)
- * keeps working unchanged. New code should call `executeNavigation` directly.
- * The decision tree (empty-href no-op, modifier/non-primary passthrough,
- * new-tab via openExternal/window.open, same-tab via navigate→fallback→
- * window.location) lives ONCE in `executeNavigation` now.
- */
-import type { ChatRuntime } from '../../../contexts/chat-runtime-context';
-import { type NavClickEvent } from './execute-navigation';
-export interface ChatNavClickInput {
-    href: string;
-    path?: string | null;
-    targetPlatform?: string | null;
-}
-export declare function handleChatNavClick(e: NavClickEvent, runtime: ChatRuntime, { href, path, targetPlatform }: ChatNavClickInput, 
-/** Host-router fallback for same-origin soft-nav when the runtime does NOT
- *  wire `navigation.navigate` (pass `useRouter().push`). */
-fallbackNavigate?: (path: string) => void): boolean;
-//# sourceMappingURL=nav-click-handler.d.ts.map

package/dist/components/chat/utils/nav-click-handler.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"nav-click-handler.d.ts","sourceRoot":"","sources":["../../../../src/components/chat/utils/nav-click-handler.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;GAWG;AAEH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,wCAAwC,CAAC;AAC1E,OAAO,EAAqB,KAAK,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAE7E,MAAM,WAAW,iBAAiB;IAChC,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,cAAc,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CAChC;AAED,wBAAgB,kBAAkB,CAChC,CAAC,EAAE,aAAa,EAChB,OAAO,EAAE,WAAW,EACpB,EAAE,IAAI,EAAE,IAAI,EAAE,cAAc,EAAE,EAAE,iBAAiB;AACjD;4DAC4D;AAC5D,gBAAgB,CAAC,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,GACxC,OAAO,CAET"}

package/src/components/chat/utils/.nav-click-handler.md

@@ -1,43 +0,0 @@
-<!-- source-hash: dd19b1c249728537a01b0a89f3b94541 -->
-Thin compatibility wrapper that forwards chat-rendered navigation link clicks to the unified `executeNavigation` primitive.
-
-## Key Components
-
-### `ChatNavClickInput`
-Interface describing the navigation target passed to the handler:
-
-| Field | Type | Description |
-|---|---|---|
-| `href` | `string` | Destination URL |
-| `path` | `string \| null` | Optional soft-nav path override |
-| `targetPlatform` | `string \| null` | Target rendering platform hint |
-
-### `handleChatNavClick`
-Delegates directly to [`executeNavigation`](https://github.com/flamingo-stack/openframe-oss-lib/blob/main/execute-navigation.ts), preserving the call shape expected by existing chat callers (chip blocks, `<ChatCardNavWrap>`, `<NavLinkAnchorViaRuntime>`). Returns a `boolean` indicating whether the click was handled.
-
-> **Deprecated.** New code should call `executeNavigation` directly. The full decision tree (empty-href no-op, modifier/non-primary passthrough, new-tab, same-tab soft-nav with fallback) lives exclusively in `execute-navigation.ts`.
-
-## Usage Example
-
-```typescript
-import { handleChatNavClick } from './nav-click-handler'
-import { useRouter } from 'next/navigation'
-
-const router = useRouter()
-
-<a
-  href={href}
-  onClick={(e) =>
-    handleChatNavClick(
-      e,
-      runtime,
-      { href, path: '/dashboard', targetPlatform: 'web' },
-      router.push, // fallback for runtimes without navigation.navigate
-    )
-  }
->
-  Dashboard
-</a>
-```
-
-The `fallbackNavigate` parameter accepts `useRouter().push` for same-origin soft-navigation when the `ChatRuntime` does not wire a `navigation.navigate` handler.

package/src/components/chat/utils/nav-click-handler.ts

@@ -1,34 +0,0 @@
-'use client';
-
-/**
- * Click router for chat-rendered nav links — chip block, `<ChatCardNavWrap>`,
- * `<NavLinkAnchorViaRuntime>`.
- *
- * @deprecated Thin wrapper around the unified `executeNavigation` primitive
- * (`execute-navigation.ts`). Kept so the existing chat callers' call shape
- * (`handleChatNavClick(e, runtime, {href,path,targetPlatform}, fallbackNavigate)`)
- * keeps working unchanged. New code should call `executeNavigation` directly.
- * The decision tree (empty-href no-op, modifier/non-primary passthrough,
- * new-tab via openExternal/window.open, same-tab via navigate→fallback→
- * window.location) lives ONCE in `executeNavigation` now.
- */
-
-import type { ChatRuntime } from '../../../contexts/chat-runtime-context';
-import { executeNavigation, type NavClickEvent } from './execute-navigation';
-
-export interface ChatNavClickInput {
-  href: string;
-  path?: string | null;
-  targetPlatform?: string | null;
-}
-
-export function handleChatNavClick(
-  e: NavClickEvent,
-  runtime: ChatRuntime,
-  { href, path, targetPlatform }: ChatNavClickInput,
-  /** Host-router fallback for same-origin soft-nav when the runtime does NOT
-   *  wire `navigation.navigate` (pass `useRouter().push`). */
-  fallbackNavigate?: (path: string) => void,
-): boolean {
-  return executeNavigation({ event: e, runtime, href, path, targetPlatform, fallbackNavigate });
-}