Context
PR #151 (Reanimated rewrite) replaces react-native's PanResponder with react-native-gesture-handler's Gesture.Manual(). As part of that rewrite, the following low-level PanResponder shim callbacks were removed from ReactNativeZoomableViewProps:
onPanResponderTerminationRequestonShouldBlockNativeResponderonStartShouldSetPanResponderonMoveShouldSetPanResponderonStartShouldSetPanResponderCaptureonMoveShouldSetPanResponderCapture
These were escape hatches for advanced gesture composition with other gesture systems (parent ScrollView, sibling Swipeable, horizontal carousels, etc.).
What's needed
There's no 1:1 mapping back to PanResponder semantics in RNGH — its composition model is different (Gesture.Simultaneous, Gesture.Race, requireExternalGestureToFail, etc.). However, consumers who relied on the removed callbacks need a working migration path.
Options to consider:
- Documented migration guide in README / SPECS — show consumers how to compose
ReactNativeZoomableView with RNGH gestures at their own level (e.g., wrap in a parent GestureDetector, use simultaneousHandlers, fail-required references).
- Expose RNGH composition primitives at the library level — accept
simultaneousHandlers / requireExternalGestureToFail props and forward to the internal Gesture.Manual().
- Accept the simplification — leave it to consumers to compose at their level using standard RNGH patterns; just document explicitly that no built-in API is provided.
Origin
Removal landed in PR #151. Tracked here so an equivalent (or explicit documentation that consumers compose at their own level) can be added before consumers hit the regression.
Context
PR #151 (Reanimated rewrite) replaces
react-native'sPanResponderwithreact-native-gesture-handler'sGesture.Manual(). As part of that rewrite, the following low-levelPanRespondershim callbacks were removed fromReactNativeZoomableViewProps:onPanResponderTerminationRequestonShouldBlockNativeResponderonStartShouldSetPanResponderonMoveShouldSetPanResponderonStartShouldSetPanResponderCaptureonMoveShouldSetPanResponderCaptureThese were escape hatches for advanced gesture composition with other gesture systems (parent ScrollView, sibling Swipeable, horizontal carousels, etc.).
What's needed
There's no 1:1 mapping back to PanResponder semantics in RNGH — its composition model is different (
Gesture.Simultaneous,Gesture.Race,requireExternalGestureToFail, etc.). However, consumers who relied on the removed callbacks need a working migration path.Options to consider:
ReactNativeZoomableViewwith RNGH gestures at their own level (e.g., wrap in a parentGestureDetector, usesimultaneousHandlers, fail-required references).simultaneousHandlers/requireExternalGestureToFailprops and forward to the internalGesture.Manual().Origin
Removal landed in PR #151. Tracked here so an equivalent (or explicit documentation that consumers compose at their own level) can be added before consumers hit the regression.