react-native-screen-transitions 3.9.0-alpha.2 → 3.9.0-alpha.3

package/lib/typescript/shared/components/boundary/hooks/use-initial-source-measurement.d.ts

@@ -1,9 +0,0 @@
-import type { BoundTag } from "../../../stores/bounds/types";
-import type { MeasureBoundary } from "../types";
-export declare const useInitialSourceMeasurement: (params: {
-    enabled: boolean;
-    measureBoundary: MeasureBoundary;
-    boundTag: BoundTag;
-    shouldAutoMeasure: boolean;
-}) => void;
-//# sourceMappingURL=use-initial-source-measurement.d.ts.map

package/lib/typescript/shared/components/boundary/hooks/use-initial-source-measurement.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"use-initial-source-measurement.d.ts","sourceRoot":"","sources":["../../../../../../src/shared/components/boundary/hooks/use-initial-source-measurement.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,8BAA8B,CAAC;AAC7D,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,UAAU,CAAC;AAGhD,eAAO,MAAM,2BAA2B,GAAI,QAAQ;IACnD,OAAO,EAAE,OAAO,CAAC;IACjB,eAAe,EAAE,eAAe,CAAC;IACjC,QAAQ,EAAE,QAAQ,CAAC;IACnB,iBAAiB,EAAE,OAAO,CAAC;CAC3B,SAmCA,CAAC"}

package/lib/typescript/shared/components/boundary/hooks/use-refresh-boundary.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"use-refresh-boundary.d.ts","sourceRoot":"","sources":["../../../../../../src/shared/components/boundary/hooks/use-refresh-boundary.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,8BAA8B,CAAC;AAC7D,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,UAAU,CAAC;AAGhD,UAAU,wBAAwB;IACjC,OAAO,EAAE,OAAO,CAAC;IACjB,QAAQ,EAAE,QAAQ,CAAC;IACnB,eAAe,EAAE,eAAe,CAAC;CACjC;AAED,eAAO,MAAM,kBAAkB,GAAI,yCAIhC,wBAAwB,SAmE1B,CAAC"}

package/lib/typescript/shared/components/boundary/portal/resolve-portal.d.ts

@@ -1,14 +0,0 @@
-import type { BoundsPortalAttachTarget } from "../../../stores/bounds/types";
-import type { BoundaryPortal } from "../types";
-/**
- * Resolves the `portal` prop against teleport availability. When
- * `react-native-teleport` is missing, portal boundaries degrade to inline
- * rendering and we warn once for the whole app.
- */
-export declare const resolveBoundaryPortal: (portal?: BoundaryPortal) => BoundaryPortal | undefined;
-/**
- * Resolves which screen host a portal'd boundary attaches to. Object form may
- * pin an explicit `attachTo`; bare `true` defaults to the current screen.
- */
-export declare const resolvePortalHost: (portal?: BoundaryPortal) => BoundsPortalAttachTarget | undefined;
-//# sourceMappingURL=resolve-portal.d.ts.map

package/lib/typescript/shared/components/boundary/portal/resolve-portal.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"resolve-portal.d.ts","sourceRoot":"","sources":["../../../../../../src/shared/components/boundary/portal/resolve-portal.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,wBAAwB,EAAE,MAAM,8BAA8B,CAAC;AAE7E,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,UAAU,CAAC;AAG/C;;;;GAIG;AACH,eAAO,MAAM,qBAAqB,GACjC,SAAS,cAAc,KACrB,cAAc,GAAG,SAanB,CAAC;AAEF;;;GAGG;AACH,eAAO,MAAM,iBAAiB,GAC7B,SAAS,cAAc,KACrB,wBAAwB,GAAG,SAM7B,CAAC"}

package/lib/typescript/shared/components/boundary/portal/utils/attachment.d.ts

@@ -1,21 +0,0 @@
-import type { BoundaryPortalAttachTarget } from "../../types";
-export type PortalAttachment = {
-    matchedScreenKey: string;
-    pairKey: string;
-};
-type ResolvePortalAttachmentTargetsParams = {
-    attachment: PortalAttachment | null;
-    currentScreenKey: string;
-    nextScreenKey?: string;
-    portalAttachTarget: BoundaryPortalAttachTarget;
-    sourcePairKey?: string;
-};
-export declare const resolvePortalAttachmentTargets: ({ attachment, currentScreenKey, nextScreenKey, portalAttachTarget, sourcePairKey, }: ResolvePortalAttachmentTargetsParams) => {
-    progressScreenKey: null;
-    targetScreenKey: null;
-} | {
-    progressScreenKey: string | null;
-    targetScreenKey: string;
-};
-export {};
-//# sourceMappingURL=attachment.d.ts.map

package/lib/typescript/shared/components/boundary/portal/utils/attachment.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"attachment.d.ts","sourceRoot":"","sources":["../../../../../../../src/shared/components/boundary/portal/utils/attachment.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,0BAA0B,EAAE,MAAM,aAAa,CAAC;AAE9D,MAAM,MAAM,gBAAgB,GAAG;IAC9B,gBAAgB,EAAE,MAAM,CAAC;IACzB,OAAO,EAAE,MAAM,CAAC;CAChB,CAAC;AAEF,KAAK,oCAAoC,GAAG;IAC3C,UAAU,EAAE,gBAAgB,GAAG,IAAI,CAAC;IACpC,gBAAgB,EAAE,MAAM,CAAC;IACzB,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,kBAAkB,EAAE,0BAA0B,CAAC;IAC/C,aAAa,CAAC,EAAE,MAAM,CAAC;CACvB,CAAC;AAEF,eAAO,MAAM,8BAA8B,GAAI,qFAM5C,oCAAoC;;;;;;CA0BtC,CAAC"}

package/src/shared/components/boundary/portal/resolve-portal.ts

@@ -1,40 +0,0 @@
-import type { BoundsPortalAttachTarget } from "../../../stores/bounds/types";
-import { logger } from "../../../utils/logger";
-import type { BoundaryPortal } from "../types";
-import { isTeleportAvailable } from "./teleport";
-
-/**
- * Resolves the `portal` prop against teleport availability. When
- * `react-native-teleport` is missing, portal boundaries degrade to inline
- * rendering and we warn once for the whole app.
- */
-export const resolveBoundaryPortal = (
-	portal?: BoundaryPortal,
-): BoundaryPortal | undefined => {
-	if (isTeleportAvailable) {
-		return portal;
-	}
-
-	if (portal) {
-		logger.warnOnce(
-			"boundary:teleport-missing",
-			"react-native-teleport is not installed and will fallback to default behavior.",
-		);
-	}
-
-	return undefined;
-};
-
-/**
- * Resolves which screen host a portal'd boundary attaches to. Object form may
- * pin an explicit `attachTo`; bare `true` defaults to the current screen.
- */
-export const resolvePortalHost = (
-	portal?: BoundaryPortal,
-): BoundsPortalAttachTarget | undefined => {
-	if (typeof portal === "object") {
-		return portal.attachTo ?? "current-screen";
-	}
-
-	return portal ? "current-screen" : undefined;
-};

package/src/shared/components/boundary/portal/utils/attachment.ts

@@ -1,48 +0,0 @@
-import type { BoundaryPortalAttachTarget } from "../../types";
-
-export type PortalAttachment = {
-	matchedScreenKey: string;
-	pairKey: string;
-};
-
-type ResolvePortalAttachmentTargetsParams = {
-	attachment: PortalAttachment | null;
-	currentScreenKey: string;
-	nextScreenKey?: string;
-	portalAttachTarget: BoundaryPortalAttachTarget;
-	sourcePairKey?: string;
-};
-
-export const resolvePortalAttachmentTargets = ({
-	attachment,
-	currentScreenKey,
-	nextScreenKey,
-	portalAttachTarget,
-	sourcePairKey,
-}: ResolvePortalAttachmentTargetsParams) => {
-	const hasCurrentAttachment = attachment?.pairKey === sourcePairKey;
-
-	if (!hasCurrentAttachment || !attachment) {
-		return {
-			progressScreenKey: null,
-			targetScreenKey: null,
-		};
-	}
-
-	// Matched-screen portals physically live in the matched destination host. If a
-	// closing destination is skipped by descriptor resolution, its own progress
-	// still owns the attach gate until this attachment is replaced or cleared.
-	if (portalAttachTarget === "matched-screen") {
-		return {
-			progressScreenKey: attachment.matchedScreenKey,
-			targetScreenKey: attachment.matchedScreenKey,
-		};
-	}
-
-	// Current-screen portals stay mounted in this screen's host, but the visual
-	// handoff is still paced by the adjacent destination transition.
-	return {
-		progressScreenKey: nextScreenKey ?? null,
-		targetScreenKey: currentScreenKey,
-	};
-};