@symbiote-native/navigation 1.0.0 → 2.0.1

package/build/core/drawer-options/index.js

@@ -1,200 +0,0 @@
-// Drawer option types + the pure swipe/geometry math. Framework-agnostic (numbers and
-// booleans only, per CLAUDE.md <prop_types_split_agnostic_vs_per_adapter>), shared verbatim by
-// every adapter. Mirrors react-navigation's Drawer prop surface (confirmed against the current
-// @react-navigation/drawer docs): drawerType 'front'/'back'/'slide'/'permanent', drawerPosition,
-// drawerWidth, overlayColor, swipeEnabled + the three swipe-tuning knobs. What is NOT ported:
-// `configureGestureHandler` - a react-native-gesture-handler-specific escape hatch with no
-// PanResponder equivalent (see packages/navigation's README / the drawer feasibility note for the
-// full gap list).
-import { isRecord } from '../guards.js';
-export const DRAWER_DEFAULT_TYPE = 'front';
-export const DRAWER_DEFAULT_POSITION = 'left';
-export const DRAWER_DEFAULT_WIDTH = 280;
-export const DRAWER_DEFAULT_OVERLAY_COLOR = 'rgba(0, 0, 0, 0.5)';
-export const DRAWER_DEFAULT_SWIPE_ENABLED = true;
-export const DRAWER_DEFAULT_SWIPE_EDGE_WIDTH = 32;
-export const DRAWER_DEFAULT_SWIPE_MIN_DISTANCE = 60;
-// react-navigation's 500 is px/second; gestureState.vx is px/ms, so the default converts.
-export const DRAWER_DEFAULT_SWIPE_MIN_VELOCITY = 0.5;
-// Exported so render-drawer.ts and the adapter can resolve the same defaults without
-// re-declaring the `??` fallback (a second copy would drift the instant a default changes).
-export function resolveDrawerWidth(options) {
-    return options.drawerWidth ?? DRAWER_DEFAULT_WIDTH;
-}
-export function resolveDrawerType(options) {
-    return options.drawerType ?? DRAWER_DEFAULT_TYPE;
-}
-export function resolveDrawerPosition(options) {
-    return options.drawerPosition ?? DRAWER_DEFAULT_POSITION;
-}
-export function isDrawerAnimated(options) {
-    return resolveDrawerType(options) !== 'permanent';
-}
-export function isDrawerOverlayVisible(options) {
-    const type = resolveDrawerType(options);
-    return type === 'front' || type === 'slide';
-}
-// front: only the panel moves (-width -> 0), content stays put, overlay fades in.
-// back: only the content moves, away from the position edge, to reveal the stationary panel;
-//   no overlay (the panel sits fully behind the content, nothing to dim).
-// slide: panel AND content move together by the same delta, overlay fades in (content still
-//   covers the panel partially as they slide in tandem, same as front visually at rest).
-// permanent: static, all zero (isDrawerAnimated() gates callers off this path already).
-export function resolveDrawerGeometry(options) {
-    const width = resolveDrawerWidth(options);
-    const type = resolveDrawerType(options);
-    const sign = resolveDrawerPosition(options) === 'left' ? 1 : -1;
-    const closedPanelX = -sign * width;
-    const openContentX = sign * width;
-    switch (type) {
-        case 'back':
-            return {
-                panelTranslateXClosed: 0,
-                panelTranslateXOpen: 0,
-                contentTranslateXClosed: 0,
-                contentTranslateXOpen: openContentX,
-                overlayOpacityClosed: 0,
-                overlayOpacityOpen: 0,
-            };
-        case 'slide':
-            return {
-                panelTranslateXClosed: closedPanelX,
-                panelTranslateXOpen: 0,
-                contentTranslateXClosed: 0,
-                contentTranslateXOpen: openContentX,
-                overlayOpacityClosed: 0,
-                overlayOpacityOpen: 1,
-            };
-        case 'front':
-        case 'permanent':
-        default:
-            return {
-                panelTranslateXClosed: closedPanelX,
-                panelTranslateXOpen: 0,
-                contentTranslateXClosed: 0,
-                contentTranslateXOpen: 0,
-                overlayOpacityClosed: 0,
-                overlayOpacityOpen: 1,
-            };
-    }
-}
-const DRAWER_PROGRESS_INPUT_RANGE = [0, 1];
-export function resolveDrawerSlotInterpolation(geometry, slot) {
-    switch (slot) {
-        case 'content':
-            return {
-                translateX: {
-                    inputRange: DRAWER_PROGRESS_INPUT_RANGE,
-                    outputRange: [geometry.contentTranslateXClosed, geometry.contentTranslateXOpen],
-                },
-            };
-        case 'overlay':
-            return {
-                opacity: {
-                    inputRange: DRAWER_PROGRESS_INPUT_RANGE,
-                    outputRange: [geometry.overlayOpacityClosed, geometry.overlayOpacityOpen],
-                },
-                translateX: {
-                    inputRange: DRAWER_PROGRESS_INPUT_RANGE,
-                    outputRange: [geometry.contentTranslateXClosed, geometry.contentTranslateXOpen],
-                },
-            };
-        case 'panel':
-            return {
-                translateX: {
-                    inputRange: DRAWER_PROGRESS_INPUT_RANGE,
-                    outputRange: [geometry.panelTranslateXClosed, geometry.panelTranslateXOpen],
-                },
-            };
-    }
-}
-// onStartShouldSetPanResponder gate: while closed, a swipe must START within swipeEdgeWidth of
-// the drawer's position edge (mirrors react-navigation's swipeEdgeWidth). While open, the whole
-// content + overlay area is fair game to drag-close, matching the intuitive "swipe anywhere to
-// dismiss an open drawer" behavior every drawer implementation (including RN's dropped native
-// DrawerLayoutAndroid) shares.
-export function isSwipeStartInEdge(startX, screenWidth, isOpen, options) {
-    if (isOpen)
-        return true;
-    const edgeWidth = options.swipeEdgeWidth ?? DRAWER_DEFAULT_SWIPE_EDGE_WIDTH;
-    return resolveDrawerPosition(options) === 'left'
-        ? startX <= edgeWidth
-        : startX >= screenWidth - edgeWidth;
-}
-// onMoveShouldSetPanResponder gate: only claim the gesture once it reads as a horizontal drag
-// (RN's own PanResponder examples use this exact dominant-axis check to stay out of a vertical
-// ScrollView's way).
-const MOVE_CLAIM_THRESHOLD = 5;
-export function isHorizontalDrag(gestureState) {
-    return (Math.abs(gestureState.dx) > MOVE_CLAIM_THRESHOLD &&
-        Math.abs(gestureState.dx) > Math.abs(gestureState.dy));
-}
-// The release-time decision, structurally the same shape as switch.ts's shouldSnapBack: a pure
-// predicate over the accumulated gesture plus the option thresholds, no framework. Distance OR
-// velocity past its threshold, in the direction that would move the drawer toward the opposite
-// of its current state, snaps it there; anything else snaps back to where it started.
-export function resolveSwipeIntent(gestureState, isOpen, options) {
-    const sign = resolveDrawerPosition(options) === 'left' ? 1 : -1;
-    // Positive `signedDelta` means "dragging toward open" for a left drawer's rightward drag (and
-    // symmetrically for a right drawer's leftward drag).
-    const signedDx = sign * gestureState.dx;
-    const signedVx = sign * gestureState.vx;
-    const minDistance = options.swipeMinDistance ?? DRAWER_DEFAULT_SWIPE_MIN_DISTANCE;
-    const minVelocity = options.swipeMinVelocity ?? DRAWER_DEFAULT_SWIPE_MIN_VELOCITY;
-    const pastDistance = Math.abs(signedDx) >= minDistance;
-    const pastVelocity = Math.abs(signedVx) >= minVelocity;
-    if (!pastDistance && !pastVelocity)
-        return isOpen ? 'open' : 'close';
-    // Velocity wins the direction call when it clears its own threshold (a fast flick can reverse
-    // a short drag); otherwise the drag distance's sign decides.
-    const towardOpen = pastVelocity ? signedVx > 0 : signedDx > 0;
-    return towardOpen ? 'open' : 'close';
-}
-export function clamp01(value) {
-    return Math.min(1, Math.max(0, value));
-}
-function toFiniteNumber(value) {
-    return typeof value === 'number' && Number.isFinite(value) ? value : undefined;
-}
-// The touch's real starting page-X, read off the raw event rather than gestureState.x0: the
-// engine's capture phase (core/engine/src/pan-responder/index.ts's
-// onStartShouldSetResponderCapture/onMoveShouldSetResponderCapture) resets gestureState before
-// the bubble-phase onStartShouldSetPanResponder/onMoveShouldSetPanResponder gates run, so x0 is
-// only populated later, inside onResponderGrant. Shaped like core/engine/src/events/index.ts's
-// readTouchPoint but not the same function: that one requires both pageX AND pageY and returns
-// an {x, y} pair for touch-history bookkeeping; this only needs pageX and is private to the
-// SET-gate below, so it stays a separate, narrower helper rather than forcing a shared contract
-// onto two callers with different needs.
-export function startPageXOf(event) {
-    const { nativeEvent } = event;
-    const direct = toFiniteNumber(nativeEvent.pageX);
-    if (direct !== undefined)
-        return direct;
-    const touches = nativeEvent.touches;
-    if (Array.isArray(touches) && isRecord(touches[0]))
-        return toFiniteNumber(touches[0].pageX);
-    return undefined;
-}
-// onPanResponderMove's drag-to-progress math: how far the touch has traveled, in progress units
-// (0..1), added to wherever the drag started from. Mirrors the SAME sign convention as
-// resolveSwipeIntent (left drawer: rightward drag is positive-toward-open).
-export function resolveDragProgress(gestureState, dragStartProgress, options) {
-    const width = resolveDrawerWidth(options);
-    const sign = resolveDrawerPosition(options) === 'right' ? -1 : 1;
-    const delta = (sign * gestureState.dx) / width;
-    return clamp01(dragStartProgress + delta);
-}
-// The composed onStartShouldSetPanResponder/onMoveShouldSetPanResponder gate: swipeEnabled ->
-// isDrawerAnimated -> isSwipeStartInEdge, then (move only) isHorizontalDrag on top. The start
-// gate omits the dominant-axis check on purpose (react-navigation's own edge-swipe idiom: claim
-// on entering the edge, confirm direction only once movement exists to measure).
-export function shouldClaimDrawerSwipe(event, gestureState, screenWidth, isOpen, options, phase) {
-    if ((options.swipeEnabled ?? DRAWER_DEFAULT_SWIPE_ENABLED) === false)
-        return false;
-    if (!isDrawerAnimated(options))
-        return false;
-    const startX = startPageXOf(event) ?? gestureState.x0;
-    if (!isSwipeStartInEdge(startX, screenWidth, isOpen, options))
-        return false;
-    return phase === 'start' ? true : isHorizontalDrag(gestureState);
-}

package/build/core/drawer-router-state/index.d.ts

@@ -1,21 +0,0 @@
-import type { IRoute } from '../navigator-state';
-export type { IRoute } from '../navigator-state';
-type IRouteEntry = IRoute<unknown>;
-export type IDrawerRouterState = Readonly<{
-    routes: readonly IRouteEntry[];
-    index: number;
-    isOpen: boolean;
-}>;
-export type IDrawerRouterAction = {
-    type: 'jumpTo';
-    name: string;
-} | {
-    type: 'openDrawer';
-} | {
-    type: 'closeDrawer';
-} | {
-    type: 'toggleDrawer';
-};
-export declare function createInitialDrawerRouterState(routes: readonly IRouteEntry[], initialRouteName?: string): IDrawerRouterState;
-export declare function drawerRouterReducer(state: IDrawerRouterState, action: IDrawerRouterAction): IDrawerRouterState;
-export declare function focusedDrawerRoute(state: IDrawerRouterState): IRouteEntry | undefined;

package/build/core/drawer-router-state/index.js

@@ -1,40 +0,0 @@
-// DrawerRouter: the logic half (framework-agnostic, zero render), sibling to navigator-state.ts
-// and tab-router-state.ts. Unlike the stack's push/pop route array, a drawer's route list is
-// FIXED at mount (one entry per declared <Drawer.Screen>, collected by the adapter exactly like
-// Stack's/Tab's collectRegistry) - the reducer only tracks which one is focused (`index`) and
-// whether the drawer panel is open. Route identity/shape is `IRoute`, reused verbatim from
-// navigator-state.ts (same convention tab-router-state.ts follows) so all three navigators share
-// one route shape.
-const INITIAL_FOCUSED_INDEX = 0;
-export function createInitialDrawerRouterState(routes, initialRouteName) {
-    if (initialRouteName === undefined) {
-        return { routes, index: INITIAL_FOCUSED_INDEX, isOpen: false };
-    }
-    const index = routes.findIndex(route => route.name === initialRouteName);
-    return { routes, index: index === -1 ? INITIAL_FOCUSED_INDEX : index, isOpen: false };
-}
-// Mirrors @react-navigation/drawer's DrawerActions: jumpTo focuses a route by NAME (TabRouter's
-// own convention, not the stack's by-key popTo) AND closes the drawer - selecting a destination
-// is itself the dismissal gesture, so a plain focus without also closing would leave the panel
-// covering the just-selected screen.
-export function drawerRouterReducer(state, action) {
-    switch (action.type) {
-        case 'jumpTo': {
-            const index = state.routes.findIndex(route => route.name === action.name);
-            if (index === -1)
-                return state;
-            return index === state.index && !state.isOpen ? state : { ...state, index, isOpen: false };
-        }
-        case 'openDrawer':
-            return state.isOpen ? state : { ...state, isOpen: true };
-        case 'closeDrawer':
-            return state.isOpen ? { ...state, isOpen: false } : state;
-        case 'toggleDrawer':
-            return { ...state, isOpen: !state.isOpen };
-        default:
-            return state;
-    }
-}
-export function focusedDrawerRoute(state) {
-    return state.routes[state.index];
-}

package/build/core/guards.d.ts

@@ -1,2 +0,0 @@
-export declare function isRecord(value: unknown): value is Record<string, unknown>;
-export declare function mergeParams(current: unknown, incoming: unknown): unknown;

package/build/core/guards.js

@@ -1,22 +0,0 @@
-// Runtime guards shared across the navigation package's core. Centralizes what used to be ~11
-// independent copies of the same `typeof value === 'object' && value !== null` check scattered
-// across core and every adapter (route-param merges, persisted-JSON validation, vnode-prop
-// narrowing, gesture-event field reads) - several of which had silently drifted on array
-// handling, one excluding arrays, another not, for the same kind of check.
-//
-// Excludes arrays: every current call site (route params, persisted navigator-state JSON,
-// touch-event objects, vnode props) only ever receives a genuine plain object, never a bare list
-// standing in for one - so `Array.isArray` narrows out a real footgun (a malformed persisted
-// value shaped like `[]` would otherwise pass this guard and fail confusingly deeper in, on a
-// missing `.key`/`.name` field, instead of here) at zero cost to the realistic inputs.
-export function isRecord(value) {
-    return typeof value === 'object' && value !== null && !Array.isArray(value);
-}
-// Mirrors @react-navigation's CommonActions.setParams: a shallow merge onto the current params,
-// but only when both sides are genuine plain objects - an array (or any other non-record) on
-// either side means a clean replace instead, never a numeric-key-mangled merge. Shared by
-// navigator-state.ts (Stack) and tab-router-state.ts (Tabs) so the two reducers can't drift on
-// this rule independently.
-export function mergeParams(current, incoming) {
-    return isRecord(current) && isRecord(incoming) ? { ...current, ...incoming } : incoming;
-}

package/build/core/header-bar-buttons.d.ts

@@ -1,9 +0,0 @@
-import type { ISymbioteEvent } from '@symbiote-native/engine';
-import type { IHeaderBarButtonItem } from './navigator-props';
-export declare function prepareHeaderBarButtonItems(items: IHeaderBarButtonItem[] | undefined, side: 'left' | 'right'): unknown[] | undefined;
-type IHeaderBarButtonDispatch = {
-    onPressHeaderBarButtonItem?: (event: ISymbioteEvent) => void;
-    onPressHeaderBarButtonMenuItem?: (event: ISymbioteEvent) => void;
-};
-export declare function buildHeaderBarButtonDispatch(leftItems: IHeaderBarButtonItem[] | undefined, rightItems: IHeaderBarButtonItem[] | undefined): IHeaderBarButtonDispatch;
-export {};

package/build/core/header-bar-buttons.js

@@ -1,163 +0,0 @@
-// Header bar-button payload + dispatch: the native-shaped `headerLeftBarButtonItems`/
-// `headerRightBarButtonItems` fold react-native-screens' own ScreenStackHeaderConfig component
-// would send down, plus the buttonId/menuId -> onPress lookup that answers RNSScreenStackHeader-
-// Config's `onPressHeaderBarButtonItem`/`onPressHeaderBarButtonMenuItem` events. Self-contained:
-// only `resolveHeaderConfigView` (screen-options.ts) calls into this file, as a black box - the
-// id-tagging scheme below is this cluster's own internal invariant, never a cross-file contract.
-import { imageStatics } from '@symbiote-native/components';
-import { processColor } from '@symbiote-native/engine';
-// RNS flattens `icon` into sfSymbolName/xcassetName/imageSource/templateSource at native-payload
-// time (both the structured `icon` field AND the flat native keys reach native - RNS's own
-// prepareHeaderBarButtonItems keeps both), and resolves image assets through the same resolver
-// the Image component uses.
-function prepareIcon(icon) {
-    if (!icon)
-        return {};
-    switch (icon.type) {
-        case 'sfSymbol':
-            return { sfSymbolName: icon.name };
-        case 'xcasset':
-            return { xcassetName: icon.name };
-        case 'imageSource':
-            return { imageSource: imageStatics.resolveAssetSource(icon.imageSource) };
-        case 'templateSource':
-            return { templateSource: imageStatics.resolveAssetSource(icon.templateSource) };
-    }
-}
-// The one id algorithm both the payload tagger (prepareMenuItems/prepareHeaderBarButtonItems)
-// and the dispatch-lookup builder (collectMenuHandlers/collectBarButtonHandlers) call - so a
-// change to the id scheme genuinely can't desync payload tagging from dispatch lookup.
-function buildMenuId(path, index, side) {
-    return `${path}-${index}-${side}`;
-}
-function buildButtonId(index, side) {
-    return `${index}-${side}`;
-}
-function prepareTitleStyle(titleStyle) {
-    if (!titleStyle)
-        return undefined;
-    return {
-        ...titleStyle,
-        color: titleStyle.color === undefined ? undefined : processColor(titleStyle.color),
-    };
-}
-function prepareBadge(badge) {
-    if (!badge)
-        return undefined;
-    return {
-        ...badge,
-        style: badge.style
-            ? {
-                ...badge.style,
-                color: badge.style.color === undefined ? undefined : processColor(badge.style.color),
-                backgroundColor: badge.style.backgroundColor === undefined
-                    ? undefined
-                    : processColor(badge.style.backgroundColor),
-            }
-            : undefined,
-    };
-}
-// onPress is captured separately into the buttonId/menuId -> handler map (collectMenuHandlers/
-// collectBarButtonHandlers below) and must never reach native: a function value fails Fabric's
-// dynamic-value serialization, which silently drops the WHOLE headerLeftBarButtonItems/
-// headerRightBarButtonItems array it's nested in - not just the one bad field - so bar buttons and
-// menu actions never reached native at all, despite the buttonId/menuId dispatch wiring itself
-// being entirely correct.
-function excludeOnPress(item) {
-    const { onPress: _onPress, ...rest } = item;
-    return rest;
-}
-// Shared fields common to the 'button' and 'menu' item variants (title/icon/tint/badge/...) - the
-// 'spacing' variant carries none of these and passes through untouched.
-function prepareSharedFields(item) {
-    return {
-        ...(item.type === 'button' ? excludeOnPress(item) : item),
-        ...prepareIcon(item.icon),
-        titleStyle: prepareTitleStyle(item.titleStyle),
-        tintColor: item.tintColor === undefined ? undefined : processColor(item.tintColor),
-        badge: prepareBadge(item.badge),
-    };
-}
-// Recursively tags every menu action with a `menuId` derived from its tree position
-// (`${path}-${index}-${side}`), mirroring RNS's own prepareMenu exactly - the id must match what
-// buildHeaderBarButtonDispatch computes below, or a press silently no-ops.
-function prepareMenuItems(menuLike, index, side, path = '') {
-    return {
-        ...menuLike,
-        items: menuLike.items.map((menuItem, menuIndex) => {
-            const currentPath = path ? `${path}.${menuIndex}` : `${menuIndex}`;
-            const icon = prepareIcon(menuItem.icon);
-            if (menuItem.type === 'submenu') {
-                return { ...menuItem, ...icon, ...prepareMenuItems(menuItem, index, side, currentPath) };
-            }
-            return {
-                ...excludeOnPress(menuItem),
-                ...icon,
-                menuId: buildMenuId(currentPath, index, side),
-            };
-        }),
-    };
-}
-// Builds the native-shaped payload react-native-screens' own ScreenStackHeaderConfig component
-// would send down (buttonId/menuId-tagged, colors processColor'd) - this is what
-// IHeaderConfigViewProps.headerLeftBarButtonItems/headerRightBarButtonItems actually carry.
-export function prepareHeaderBarButtonItems(items, side) {
-    if (!items)
-        return undefined;
-    return items.map((item, index) => {
-        if (item.type === 'spacing')
-            return item;
-        const prepared = prepareSharedFields(item);
-        if (item.type === 'button')
-            return { ...prepared, buttonId: buildButtonId(index, side) };
-        return { ...prepared, menu: prepareMenuItems(item.menu, index, side) };
-    });
-}
-function collectMenuHandlers(items, index, side, path, handlers) {
-    items.forEach((item, menuIndex) => {
-        const currentPath = path ? `${path}.${menuIndex}` : `${menuIndex}`;
-        if (item.type === 'submenu') {
-            collectMenuHandlers(item.items, index, side, currentPath, handlers);
-            return;
-        }
-        handlers.set(buildMenuId(currentPath, index, side), item.onPress);
-    });
-}
-function collectBarButtonHandlers(items, side, buttonHandlers, menuHandlers) {
-    items?.forEach((item, index) => {
-        if (item.type === 'button') {
-            buttonHandlers.set(buildButtonId(index, side), item.onPress);
-        }
-        else if (item.type === 'menu') {
-            collectMenuHandlers(item.menu.items, index, side, '', menuHandlers);
-        }
-    });
-}
-function readStringField(record, key) {
-    const value = record[key];
-    return typeof value === 'string' ? value : undefined;
-}
-// The buttonId/menuId → onPress lookup is built independently from prepareHeaderBarButtonItems'
-// native payload (rather than re-parsing it back out of the `unknown[]` result), over the
-// ORIGINAL typed items - but both sides call the same buildMenuId/buildButtonId, so the id
-// scheme lives in one place and can't desync payload tagging from dispatch lookup.
-export function buildHeaderBarButtonDispatch(leftItems, rightItems) {
-    const buttonHandlers = new Map();
-    const menuHandlers = new Map();
-    collectBarButtonHandlers(leftItems, 'left', buttonHandlers, menuHandlers);
-    collectBarButtonHandlers(rightItems, 'right', buttonHandlers, menuHandlers);
-    if (buttonHandlers.size === 0 && menuHandlers.size === 0)
-        return {};
-    return {
-        onPressHeaderBarButtonItem: event => {
-            const buttonId = readStringField(event.nativeEvent, 'buttonId');
-            if (buttonId !== undefined)
-                buttonHandlers.get(buttonId)?.();
-        },
-        onPressHeaderBarButtonMenuItem: event => {
-            const menuId = readStringField(event.nativeEvent, 'menuId');
-            if (menuId !== undefined)
-                menuHandlers.get(menuId)?.();
-        },
-    };
-}

package/build/core/index.d.ts

@@ -1,29 +0,0 @@
-export * from './constants';
-export { createInitialNavigatorState, navigatorReducer, computeActivityState, isTopRoute, } from './navigator-state';
-export type { IRoute, INavigatorState, INavigatorAction } from './navigator-state';
-export type { IStackAnimation, IStackPresentation, IHeaderBackButtonDisplayMode, IHeaderUserInterfaceStyle, IOptionalBooleanNativeProp, ISheetAllowedDetents, ISheetLargestUndimmedDetent, ISheetInitialDetent, IHeaderBarButtonIcon, IHeaderBarButtonItemBadge, IHeaderBarButtonItemAction, IHeaderBarButtonMenuAction, IHeaderBarButtonSubmenu, IHeaderBarButtonItemMenu, IHeaderBarButtonItemSpacing, IHeaderBarButtonItem, ISearchBarAutoCapitalize, ISearchBarPlacement, ISearchBarOptions, IScreenOrientation, IScreenOptions, INavigatorPlatform, IScreenViewProps, IHeaderConfigViewProps, IStackViewProps, ISearchBarViewProps, } from './navigator-props';
-export { resolveHeaderConfigView, resolveScreenView, resolveSearchBarView } from './screen-options';
-export { buildSearchBarHandle } from './search-bar-commands';
-export type { ISearchBarCommands } from './search-bar-commands';
-export { resolveScreenProps, resolveStackProps, renderHeaderConfig, resolveSearchBarProps, resolveScreenContentWrapperStyle, resolveScreenViewName, isHeaderInModal, resolveHeaderInModalStackStyle, resolveHeaderInModalScreenStyle, buildSearchBarPassthrough, resolveScreenRenderPlan, } from './render-stack';
-export type { IScreenRenderPlanInput, IScreenRenderPlan } from './render-stack';
-export { serializeNavigatorState, deserializeNavigatorState } from './state-persistence';
-export { createNavigationEmitter, diffFocusedRoute, NAVIGATION_EVENT_FOCUS, NAVIGATION_EVENT_BLUR, NAVIGATION_EVENT_STATE, NAVIGATION_EVENT_BEFORE_REMOVE, } from './navigation-events';
-export type { INavigationEmitter, INavigationEventListener, INavigationEventName, IFocusTransition, } from './navigation-events';
-export { isRecord } from './guards';
-export { createInitialTabState, tabRouterReducer, isFocusedRoute } from './tab-router-state';
-export type { ITabRouterState, ITabRouterAction } from './tab-router-state';
-export type { ITabBarIcon, ITabOptions } from './tab-options';
-export { renderTabBarItem, renderTabBar } from './render-tabs';
-export type { ITabBarItemView, ITabBarViewProps } from './render-tabs';
-export { resolveRouteFromUrl, resolveUrlFromRoute } from './linking-config';
-export type { ILinkingConfig, IScreenLinkingConfig } from './linking-config';
-export { createInitialDrawerRouterState, drawerRouterReducer, focusedDrawerRoute, } from './drawer-router-state';
-export type { IDrawerRouterState, IDrawerRouterAction } from './drawer-router-state';
-export type { IDrawerType, IDrawerPosition, IDrawerOptions, IDrawerScreenOptions, IDrawerGeometry, ISwipeIntent, } from './drawer-options';
-export { DRAWER_DEFAULT_TYPE, DRAWER_DEFAULT_POSITION, DRAWER_DEFAULT_WIDTH, DRAWER_DEFAULT_OVERLAY_COLOR, DRAWER_DEFAULT_SWIPE_ENABLED, DRAWER_DEFAULT_SWIPE_EDGE_WIDTH, DRAWER_DEFAULT_SWIPE_MIN_DISTANCE, DRAWER_DEFAULT_SWIPE_MIN_VELOCITY, resolveDrawerType, resolveDrawerPosition, resolveDrawerWidth, isDrawerAnimated, isDrawerOverlayVisible, resolveDrawerGeometry, isSwipeStartInEdge, isHorizontalDrag, resolveSwipeIntent, clamp01, startPageXOf, resolveDragProgress, shouldClaimDrawerSwipe, resolveDrawerSlotInterpolation, } from './drawer-options';
-export type { IDrawerInterpolationRange, IDrawerContentSlotInterpolation, IDrawerOverlaySlotInterpolation, IDrawerPanelSlotInterpolation, } from './drawer-options';
-export { renderDrawer, drawerChildOrder } from './render-drawer';
-export type { IDrawerSlot, IDrawerViewProps } from './render-drawer';
-export type { INavigatorHandle, ITabNavigatorHandle, IDrawerNavigatorHandle, IDrawerDescriptorMap, IAnyNavigatorHandle, } from './navigator-handles';
-export { isStackNavigatorHandle, isTabNavigatorHandle, isDrawerNavigatorHandle, } from './navigator-handles';

package/build/core/index.js

@@ -1,32 +0,0 @@
-// @symbiote-native/navigation (core): the framework-agnostic half of the native stack navigator -
-// a pure route-stack reducer plus the react-native-screens prop folds and native-leaf prop
-// resolvers. symbiote ships zero runtime metadata for RNSScreen/RNSScreenStack/
-// RNSScreenStackHeaderConfig - the engine derives their events and color processors from
-// react-native-screens' own ViewConfig - so this layer is the pure JS every adapter reuses
-// verbatim, supplying only its lifecycle (route-key generation, useReducer/reactive state) and
-// the descriptor bridge.
-export * from './constants.js';
-export { createInitialNavigatorState, navigatorReducer, computeActivityState, isTopRoute, } from './navigator-state/index.js';
-export { resolveHeaderConfigView, resolveScreenView, resolveSearchBarView } from './screen-options.js';
-export { buildSearchBarHandle } from './search-bar-commands.js';
-export { resolveScreenProps, resolveStackProps, renderHeaderConfig, resolveSearchBarProps, resolveScreenContentWrapperStyle, resolveScreenViewName, isHeaderInModal, resolveHeaderInModalStackStyle, resolveHeaderInModalScreenStyle, buildSearchBarPassthrough, resolveScreenRenderPlan, } from './render-stack.js';
-export { serializeNavigatorState, deserializeNavigatorState } from './state-persistence/index.js';
-export { createNavigationEmitter, diffFocusedRoute, NAVIGATION_EVENT_FOCUS, NAVIGATION_EVENT_BLUR, NAVIGATION_EVENT_STATE, NAVIGATION_EVENT_BEFORE_REMOVE, } from './navigation-events/index.js';
-// Runtime guards shared across core (and re-exported for adapters narrowing their own untyped
-// inputs - vnode props, gesture/event data, persisted JSON) - see guards.ts's header for which
-// call sites this consolidates and why array-exclusion is the right default everywhere it's used.
-export { isRecord } from './guards.js';
-// Bottom-tabs navigator: a FOCUSED-INDEX router (not a stack - see tab-router-state.ts) driving
-// a pure-JS tab bar render, framework-agnostic and shared verbatim by every adapter.
-export { createInitialTabState, tabRouterReducer, isFocusedRoute } from './tab-router-state/index.js';
-export { renderTabBarItem, renderTabBar } from './render-tabs.js';
-// Linking config: resolves a URL to a route (and back), the piece @react-navigation's
-// NavigationContainer `linking` prop provides on top of the framework-agnostic Linking module.
-export { resolveRouteFromUrl, resolveUrlFromRoute } from './linking-config/index.js';
-// Drawer navigator: an OPEN/CLOSED-flag router over a fixed route list (see
-// drawer-router-state.ts's header for why it isn't a push/pop stack), a pure swipe/geometry math
-// module, and a Descriptor render fn - all framework-agnostic, shared verbatim by every adapter.
-export { createInitialDrawerRouterState, drawerRouterReducer, focusedDrawerRoute, } from './drawer-router-state/index.js';
-export { DRAWER_DEFAULT_TYPE, DRAWER_DEFAULT_POSITION, DRAWER_DEFAULT_WIDTH, DRAWER_DEFAULT_OVERLAY_COLOR, DRAWER_DEFAULT_SWIPE_ENABLED, DRAWER_DEFAULT_SWIPE_EDGE_WIDTH, DRAWER_DEFAULT_SWIPE_MIN_DISTANCE, DRAWER_DEFAULT_SWIPE_MIN_VELOCITY, resolveDrawerType, resolveDrawerPosition, resolveDrawerWidth, isDrawerAnimated, isDrawerOverlayVisible, resolveDrawerGeometry, isSwipeStartInEdge, isHorizontalDrag, resolveSwipeIntent, clamp01, startPageXOf, resolveDragProgress, shouldClaimDrawerSwipe, resolveDrawerSlotInterpolation, } from './drawer-options/index.js';
-export { renderDrawer, drawerChildOrder } from './render-drawer.js';
-export { isStackNavigatorHandle, isTabNavigatorHandle, isDrawerNavigatorHandle, } from './navigator-handles/index.js';

package/build/core/linking-config/index.d.ts

@@ -1,13 +0,0 @@
-import type { IRoute } from '../navigator-state';
-export type IScreenLinkingConfig = string | {
-    path?: string;
-    screens?: Record<string, IScreenLinkingConfig>;
-};
-export type ILinkingConfig = {
-    prefixes: string[];
-    config: {
-        screens: Record<string, IScreenLinkingConfig>;
-    };
-};
-export declare function resolveRouteFromUrl(config: ILinkingConfig, url: string): IRoute<unknown> | null;
-export declare function resolveUrlFromRoute(config: ILinkingConfig, route: IRoute<unknown>): string | null;