@momo-kits/foundation 0.164.1-beta.5 → 0.164.1-beta.7

package/Application/StackScreen.tsx

@@ -6,7 +6,7 @@ import Navigation from './Navigation';
 import { ApplicationContext, MiniAppContext, ScreenContext } from '../Context';
 import { GridSystem } from '../Layout';
 import { version } from '../package.json';
-import { useAppState, useSwipeBackHaptic } from './utils';
+import { useAppState } from './utils';
 import { TooltipPortalHost, TooltipPortalProvider } from './TooltipPortal';
 
 const runAfterInteractions = InteractionManager.runAfterInteractions;
@@ -51,7 +51,6 @@ const StackScreen: React.FC<any> = props => {
   const navigation = useRef(new Navigation(props.navigation, context)).current;
   const heightHeader = useHeaderHeight();
   const { isBackgroundToForeground } = useAppState();
-  useSwipeBackHaptic();
 
   const data = {
     ...initialParams,

package/Application/utils.tsx

@@ -6,7 +6,6 @@ import React, {
   useRef,
 } from 'react';
 import {
-  CardAnimationContext,
   CardStyleInterpolators,
   StackNavigationOptions,
   TransitionPresets,
@@ -22,7 +21,6 @@ import { Animated, AppState, NativeModules, Platform } from 'react-native';
 import type { SharedValue } from 'react-native-reanimated';
 import { useSharedValue } from 'react-native-reanimated';
 import {
-  ApplicationContext,
   MiniAppContext,
   ScreenContext,
   TrackingScopeContext,
@@ -334,139 +332,6 @@ const useNativeCanGoBack = () => {
   );
 };
 
-/**
- * fraction of screen width at which releasing commits the pop. deliberately
- * pinned to react-navigation's own rule: Card.tsx (GestureState.END,
- * @react-navigation/stack 7.4.2) closes the card when
- * `(translation + velocity * gestureVelocityImpact) * inverted > distance / 2`
- * with `distance = layout.width` for a horizontal gesture, and exposes no
- * option to override it. so the tick means "release now and you go back"
- * instead of marking a distance of its own — keep the two in sync.
- *
- * mid drag only translation is known, velocity exists solely at release, so a
- * short fast flick can commit without ever crossing this and pops with no
- * tick. that asymmetry is intended: modelling velocity per frame would tick
- * on swipes that then do not commit, which is the worse error
- */
-const SWIPE_BACK_HAPTIC_COMMIT_RATIO = 0.5;
-
-const readAnimatedValue = (node: unknown, fallback: number): number => {
-  const getValue = (node as { __getValue?: () => unknown } | undefined)
-    ?.__getValue;
-  if (typeof getValue !== 'function') {
-    return fallback;
-  }
-
-  const value = getValue.call(node);
-  return typeof value === 'number' ? value : fallback;
-};
-
-/**
- * `current.progress` is built as `gesture.interpolate(...)`, so its parent is
- * the raw pan translation the finger drives. Private react-navigation / RN
- * shape, verified against @react-navigation/stack 7.4.2 + react-native 0.80.1
- * — duck-typed so a rename degrades to "no haptic" instead of a crash.
- */
-const getSwipeGestureValue = (
-  progress?: Animated.AnimatedInterpolation<number>,
-): Animated.Value | undefined => {
-  const parent = (progress as { _parent?: Animated.Value } | undefined)
-    ?._parent;
-
-  return typeof parent?.addListener === 'function' &&
-    typeof parent?.removeListener === 'function'
-    ? parent
-    : undefined;
-};
-
-/**
- * one light tick once the swipe back passes the point where releasing commits
- * the pop. iOS only, mirroring `gestureEnabled` in getStackOptions.
- *
- * both listeners are installed on mount and never lazily inside the gesture:
- * on the New Architecture `addListener` queues `startListeningToAnimatedNodeValue`
- * via `queueOperationBlock`, and that queue is only drained by a React mount
- * commit — which never happens during a native driven pan. subscribing when the
- * swipe starts installs an observer that the release flush tears down again
- * before a single frame is delivered, so it must stay on mount.
- *
- * `gesture` also drives the programmatic push and pop animations, so it is the
- * JS `isSwiping` flag, not the subscription lifetime, that keeps the tick
- * exclusive to a real finger drag.
- */
-const useSwipeBackHaptic = () => {
-  const { navigator } = useContext<any>(ApplicationContext);
-  const animation = useContext(CardAnimationContext);
-
-  /**
-   * the latch has to outlive the effect. `animation` identity changes on every
-   * navigator render, so a `hasFired` local re-arms several times per drag and
-   * the tick then repeats on every frame past the threshold
-   */
-  const hasFired = useRef(false);
-
-  useEffect(() => {
-    if (Platform.OS !== 'ios' || !animation) {
-      return;
-    }
-
-    const { swiping, inverted, current, layouts } = animation;
-    const gesture = getSwipeGestureValue(current?.progress);
-    if (!gesture || typeof swiping?.addListener !== 'function') {
-      return;
-    }
-
-    /**
-     * `animation` identity is not stable, so this effect can re-run mid swipe.
-     * seed from the live value instead of waiting for a 0 -> 1 transition that
-     * has already been missed
-     */
-    let isSwiping = readAnimatedValue(swiping, 0) === 1;
-
-    /**
-     * sign, not magnitude: a leftward overdrag reports a negative
-     * translation and must not count as progress toward dismissal
-     */
-    const direction = readAnimatedValue(inverted, 1);
-
-    /**
-     * plain JS numbers, not animated nodes (`StackCardInterpolationProps`).
-     * screen layout can still be unmeasured on an early render, and a zero
-     * width would put the threshold at 0 and tick the moment the finger moves
-     */
-    const commitThreshold =
-      (layouts?.screen?.width ?? 0) * SWIPE_BACK_HAPTIC_COMMIT_RATIO;
-
-    const swipingListener = swiping.addListener(({ value }) => {
-      isSwiping = value === 1;
-      if (!isSwiping) {
-        hasFired.current = false;
-      }
-    });
-
-    const gestureListener = gesture.addListener(({ value: translation }) => {
-      if (!isSwiping || commitThreshold <= 0) {
-        return;
-      }
-
-      if (translation * direction < commitThreshold) {
-        hasFired.current = false;
-        return;
-      }
-
-      if (!hasFired.current) {
-        hasFired.current = true;
-        navigator?.maxApi?.triggerEventVibration?.('light');
-      }
-    });
-
-    return () => {
-      gesture.removeListener(gestureListener);
-      swiping.removeListener(swipingListener);
-    };
-  }, [animation, navigator]);
-};
-
 /**
  * Union of the two animation runtimes an internal foundation component might
  * receive. Public Screen props still accept React Native Animated.Value only;
@@ -515,5 +380,4 @@ export {
   useAppState,
   useNativeCanGoBack,
   useNormalizedSharedValue,
-  useSwipeBackHaptic,
 };

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@momo-kits/foundation",
-    "version": "0.164.1-beta.5",
+    "version": "0.164.1-beta.7",
     "description": "React Native Component Kits",
     "main": "index.ts",
     "scripts": {},