Export with legacy prefix

Author: m-bert

apps/common-app/src/legacy/basic/pagerAndDrawer/index.android.tsx

@@ -2,11 +2,11 @@ import ViewPagerAndroid from '@react-native-community/viewpager';
 import React, { Component } from 'react';
 import { StyleSheet, Text, View } from 'react-native';
 import {
-  createNativeWrapper,
+  legacy_createNativeWrapper,
   LegacyDrawerLayoutAndroid,
 } from 'react-native-gesture-handler';
 
-const WrappedViewPagerAndroid = createNativeWrapper(ViewPagerAndroid, {
+const WrappedViewPagerAndroid = legacy_createNativeWrapper(ViewPagerAndroid, {
   disallowInterruption: true,
 });
 

apps/common-app/src/legacy/release_tests/combo/index.tsx

@@ -16,7 +16,7 @@ import {
   TapGestureHandler,
   TextInput,
   RectButton,
-  createNativeWrapper,
+  legacy_createNativeWrapper,
   TapGestureHandlerStateChangeEvent,
 } from 'react-native-gesture-handler';
 import Slider from '@react-native-community/slider';
@@ -30,7 +30,7 @@ import { PressBox } from '../../basic/multitap';
 import { LoremIpsum } from '../../../common';
 import { InfoButton } from './InfoButton';
 
-const WrappedSlider = createNativeWrapper(Slider, {
+const WrappedSlider = legacy_createNativeWrapper(Slider, {
   shouldCancelWhenOutside: false,
   shouldActivateOnStart: true,
   disallowInterruption: true,

packages/docs-gesture-handler/docs/guides/upgrading-to-3.mdx

@@ -281,6 +281,10 @@ Other components have also been internally rewritten using the new hook API but
 
 </details>
 
+### createNativeWrapper
+
+`createNativeWrapper` is now exported as `legacy_createNativeWrapper`.
+
 ## Replaced types
 
 Most of the types, like `TapGesture`, are still present in Gesture Handler 3. However, they are now used in new hook API. Types for old API now have `Legacy` prefix, e.g. `TapGesture` becomes `LegacyTapGesture`.

packages/react-native-gesture-handler/src/index.ts

@@ -52,7 +52,7 @@ export { PanGestureHandler } from './handlers/PanGestureHandler';
 export { PinchGestureHandler } from './handlers/PinchGestureHandler';
 export { RotationGestureHandler } from './handlers/RotationGestureHandler';
 export { FlingGestureHandler } from './handlers/FlingGestureHandler';
-export { default as createNativeWrapper } from './handlers/createNativeWrapper';
+export { default as legacy_createNativeWrapper } from './handlers/createNativeWrapper';
 export type { NativeViewGestureHandlerProps } from './handlers/NativeViewGestureHandler';
 export { GestureDetector as LegacyGestureDetector } from './handlers/gestures/GestureDetector';
 export { GestureObjects as Gesture } from './handlers/gestures/gestureObjects';

skills/gesture-handler-3-migration/SKILL.md

@@ -35,13 +35,15 @@ The exception to thait is `Gesture.ForceTouch` which DOES NOT have a counterpart
 #### Callback changes
 
 In Gesture Handler 3 some of the callbacks were renamed, namely:
+
 - `onStart` -> `onActivate`
 - `onEnd` -> `onDeactivate`
 - `onTouchesCancelled` -> `onTouchesCancel`
 
 In the hooks API `onChange` is no longer available. Instead the `*change*` properties were moved to the event available inside `onUpdate`.
 
 All callbacks of a gesture are now using the same type:
+
 - `usePanGesture()` -> `PanGestureEvent`
 - `useTapGesture()` -> `TapGestureEvent`
 - `useLongPressGesture()` -> `LongPressGestureEvent`
@@ -53,6 +55,7 @@ All callbacks of a gesture are now using the same type:
 - `useManualGesture()` -> `ManualGestureEvent`
 
 The exception to this is touch events:
+
 - `onTouchesDown`
 - `onTouchesUp`
 - `onTouchesMove`
@@ -65,12 +68,14 @@ Where each callback receives `GestureTouchEvent` regardless of the hook used.
 In Gesture Handler 3, `stateManager` is no longer passed to `TouchEvent` callbacks. Instead, you should use the global `GestureStateManager`.
 
 `GestureStateManager` provides methods for imperative state management:
+
 - .begin(handlerTag: number)
 - .activate(handlerTag: number)
 - .deactivate(handlerTag: number) (.end() in the old API)
 - .fail(handlerTag: number)
 
 `handlerTag` can be obtained in two ways:
+
 1. From the gesture object returned by the hook (`gesture.handlerTag`)
 2. From the event inside callback (`event.handlerTag`)
 
@@ -83,13 +88,15 @@ Callback definitions CANNOT reference the gesture that's being defined. In this
 `Gesture.Simultaneous(gesture1, gesture2);` becomes `useSimultaneousGestures(pan1, pan2);`
 
 All relations from the old API and their counterparts in the new one:
+
 - `Gesture.Race()` -> `useCompetingGestures()`
 - `Gesture.Simultaneous()` -> `useSimultaneousGestures()`
 - `Gesture.Exclusive()` -> `useExclusiveGestures()`
 
 #### Cross components relations properties
 
 Properties used to define cross-components interactions were renamed:
+
 - `.simultaneousWithExternalGesture` -> `simultaneousWith:`
 - `.requireExternalGestureToFail` -> `requireToFail:`
 - `.blocksExternalGesture` -> `block:`
@@ -164,6 +171,8 @@ The implementation of buttons has been updated, resolving most button-related is
 
 Other components have also been internally rewritten using the new hook API but are exported under their original names, so no changes are necessary on your part. However, if you need to use the previous implementation for any reason, the legacy components are also available and are prefixed with `Legacy`, e.g., `ScrollView` is now available as `LegacyScrollView`.
 
+Rename all instances of createNativeWrapper to legacy_createNativeWrapper. This includes both the import statements and the function calls.
+
 ### Replaced types
 
 Most of the types used in the builder API, like `TapGesture`, are still present in Gesture Handler 3. However, they are now used in new hook API. Types for builder API now have `Legacy` prefix, e.g. `TapGesture` becomes `LegacyTapGesture`.