Follow-up from PR #151 review thread: #151 (comment)
Elliott confirmed the existing pull-to-close behaviour also works with expo-router (which uses native-stack under the hood). Worth adding an expo-router-based screen to the example app so we have an extra regression test case alongside the current react-navigation / react-native-screens setup.
Why deferred
Out of scope for PR #151 (the Reanimated rewrite). Pure example-app additions, no library code change required. Filing here so we don't lose it after the PR lands.
Proposed scope
- Add
expo-router to the example app's deps.
- Add one or two demo routes (e.g.
formSheet / pageSheet) wrapping ReactNativeZoomableView, mirroring the react-navigation cases.
- Verify pinch / pan / pull-to-close still behave as expected on iOS + Android.
Follow-up from PR #151 review thread: #151 (comment)
Elliott confirmed the existing pull-to-close behaviour also works with
expo-router(which uses native-stack under the hood). Worth adding anexpo-router-based screen to the example app so we have an extra regression test case alongside the currentreact-navigation/react-native-screenssetup.Why deferred
Out of scope for PR #151 (the Reanimated rewrite). Pure example-app additions, no library code change required. Filing here so we don't lose it after the PR lands.
Proposed scope
expo-routerto the example app's deps.formSheet/pageSheet) wrappingReactNativeZoomableView, mirroring thereact-navigationcases.