Files
react-native/Libraries/Interaction/PanResponder.d.ts
T
Nick Gerleman 5d26ceaa23 Fixup TS Organization (#35169)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/35169

This reorganizes typing structure a bit.

`Utilities.d.ts` was originally added for utilitiy types but I ended up leaving it a grab bag of types that didn't belong to any individual bit of code. Out of what is in it right now, `Insets` was actually public, and seems to have been imported.

We also run into files around the renderer which are [currently overwritten](https://github.com/facebook/react-native/commits/e286da25fc83324363486eb668806aca179f74b3/Libraries/Renderer/implementations/ReactNativeRenderer.d.ts) by the React sync script.

Finally, all of the top-level imports of `Utilities` were auto-generated by VS Code, but fail in real apps. I think this is because our tsconfig sets a `baseUrl` to allow resolution from the types folder, so the tooling in the RN repo will use that, but it breaks in real apps that don't have that mapping.

This splits all these up into a couple separate directories that are hopefully easier to reason about, and removes `Omit` which has been a builtin type for quite some time (we were actually already using built-in `Omit`).

Changelog:
[General][Fixed] - Fixup TS Organization

Reviewed By: cipolleschi

Differential Revision: D40932319

fbshipit-source-id: 0b6e3e3eda603885b4dc01dcb9f5233aa546d128
2022-11-02 14:58:37 -07:00

203 lines
5.8 KiB
TypeScript

/**
* Copyright (c) Meta Platforms, Inc. and affiliates.
*
* This source code is licensed under the MIT license found in the
* LICENSE file in the root directory of this source tree.
*
* @format
*/
import {GestureResponderHandlers} from '../../types/public/ReactNativeRenderer';
import {GestureResponderEvent} from '../Types/CoreEventTypes';
export interface PanResponderGestureState {
/**
* ID of the gestureState- persisted as long as there at least one touch on
*/
stateID: number;
/**
* the latest screen coordinates of the recently-moved touch
*/
moveX: number;
/**
* the latest screen coordinates of the recently-moved touch
*/
moveY: number;
/**
* the screen coordinates of the responder grant
*/
x0: number;
/**
* the screen coordinates of the responder grant
*/
y0: number;
/**
* accumulated distance of the gesture since the touch started
*/
dx: number;
/**
* accumulated distance of the gesture since the touch started
*/
dy: number;
/**
* current velocity of the gesture
*/
vx: number;
/**
* current velocity of the gesture
*/
vy: number;
/**
* Number of touches currently on screen
*/
numberActiveTouches: number;
// All `gestureState` accounts for timeStamps up until:
_accountsForMovesUpTo: number;
}
/**
* @see documentation of GestureResponderHandlers
*/
export interface PanResponderCallbacks {
onMoveShouldSetPanResponder?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => boolean)
| undefined;
onStartShouldSetPanResponder?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => boolean)
| undefined;
onPanResponderGrant?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => void)
| undefined;
onPanResponderMove?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => void)
| undefined;
onPanResponderRelease?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => void)
| undefined;
onPanResponderTerminate?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => void)
| undefined;
onMoveShouldSetPanResponderCapture?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => boolean)
| undefined;
onStartShouldSetPanResponderCapture?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => boolean)
| undefined;
onPanResponderReject?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => void)
| undefined;
onPanResponderStart?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => void)
| undefined;
onPanResponderEnd?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => void)
| undefined;
onPanResponderTerminationRequest?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => boolean)
| undefined;
onShouldBlockNativeResponder?:
| ((
e: GestureResponderEvent,
gestureState: PanResponderGestureState,
) => boolean)
| undefined;
}
export interface PanResponderInstance {
panHandlers: GestureResponderHandlers;
}
/**
* PanResponder reconciles several touches into a single gesture.
* It makes single-touch gestures resilient to extra touches,
* and can be used to recognize simple multi-touch gestures.
*
* It provides a predictable wrapper of the responder handlers provided by the gesture responder system.
* For each handler, it provides a new gestureState object alongside the normal event.
*/
export interface PanResponderStatic {
/**
* @param config Enhanced versions of all of the responder callbacks
* that provide not only the typical `ResponderSyntheticEvent`, but also the
* `PanResponder` gesture state. Simply replace the word `Responder` with
* `PanResponder` in each of the typical `onResponder*` callbacks. For
* example, the `config` object would look like:
*
* - `onMoveShouldSetPanResponder: (e, gestureState) => {...}`
* - `onMoveShouldSetPanResponderCapture: (e, gestureState) => {...}`
* - `onStartShouldSetPanResponder: (e, gestureState) => {...}`
* - `onStartShouldSetPanResponderCapture: (e, gestureState) => {...}`
* - `onPanResponderReject: (e, gestureState) => {...}`
* - `onPanResponderGrant: (e, gestureState) => {...}`
* - `onPanResponderStart: (e, gestureState) => {...}`
* - `onPanResponderEnd: (e, gestureState) => {...}`
* - `onPanResponderRelease: (e, gestureState) => {...}`
* - `onPanResponderMove: (e, gestureState) => {...}`
* - `onPanResponderTerminate: (e, gestureState) => {...}`
* - `onPanResponderTerminationRequest: (e, gestureState) => {...}`
* - `onShouldBlockNativeResponder: (e, gestureState) => {...}`
*
* In general, for events that have capture equivalents, we update the
* gestureState once in the capture phase and can use it in the bubble phase
* as well.
*
* Be careful with onStartShould* callbacks. They only reflect updated
* `gestureState` for start/end events that bubble/capture to the Node.
* Once the node is the responder, you can rely on every start/end event
* being processed by the gesture and `gestureState` being updated
* accordingly. (numberActiveTouches) may not be totally accurate unless you
* are the responder.
*/
create(config: PanResponderCallbacks): PanResponderInstance;
}
export const PanResponder: PanResponderStatic;
export type PanResponder = PanResponderStatic;