mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
Nick Gerleman
8cdc9e7f04
Summary: React Native's TS definitions are currently mostly stored in one monolithic file. This change splits the definitions up to correspond to the source files they came from, and are placed next to the source files. I think this should help inform, and make it easy to update the TS declarations when touching the Flow file. I noticed as part of the change that the typings have not yet removed many APIs that were removed from RN. This is bad, since it means using the removed/non-functional API doesn't cause typechecker errors. Locating typings next to source should prevent that from being able to happen. The organization here means individual TS declarations can declare what will be in the RN entrypoint, which is a little confusing. Seems like a good potential next refactor, beyond the literal translation I did. Changelog: [General][Changed] - Place TS Declarations Alongside Source Files Reviewed By: lunaleaps, rshest Differential Revision: D39796598 fbshipit-source-id: b36366466fd1976bdd2d4c8f7a4104a33c457a07
68 lines
2.3 KiB
TypeScript
68 lines
2.3 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 type * as React from 'react';
|
|
import {Constructor, TimerMixin} from 'Utilities';
|
|
import {NativeMethods} from '../../Renderer/shims/ReactNativeTypes';
|
|
import {ColorValue, StyleProp} from '../../StyleSheet/StyleSheet';
|
|
import {ViewStyle} from '../../StyleSheet/StyleSheetTypes';
|
|
import {TouchableMixin} from './Touchable';
|
|
import {TouchableWithoutFeedbackProps} from './TouchableWithoutFeedback';
|
|
|
|
/**
|
|
* @see https://reactnative.dev/docs/touchablehighlight#props
|
|
*/
|
|
export interface TouchableHighlightProps extends TouchableWithoutFeedbackProps {
|
|
/**
|
|
* Determines what the opacity of the wrapped view should be when touch is active.
|
|
*/
|
|
activeOpacity?: number | undefined;
|
|
|
|
/**
|
|
*
|
|
* Called immediately after the underlay is hidden
|
|
*/
|
|
onHideUnderlay?: (() => void) | undefined;
|
|
|
|
/**
|
|
* Called immediately after the underlay is shown
|
|
*/
|
|
onShowUnderlay?: (() => void) | undefined;
|
|
|
|
/**
|
|
* @see https://reactnative.dev/docs/view#style
|
|
*/
|
|
style?: StyleProp<ViewStyle> | undefined;
|
|
|
|
/**
|
|
* The color of the underlay that will show through when the touch is active.
|
|
*/
|
|
underlayColor?: ColorValue | undefined;
|
|
}
|
|
|
|
/**
|
|
* A wrapper for making views respond properly to touches.
|
|
* On press down, the opacity of the wrapped view is decreased,
|
|
* which allows the underlay color to show through, darkening or tinting the view.
|
|
* The underlay comes from adding a view to the view hierarchy,
|
|
* which can sometimes cause unwanted visual artifacts if not used correctly,
|
|
* for example if the backgroundColor of the wrapped view isn't explicitly set to an opaque color.
|
|
*
|
|
* NOTE: TouchableHighlight supports only one child
|
|
* If you wish to have several child components, wrap them in a View.
|
|
*
|
|
* @see https://reactnative.dev/docs/touchablehighlight
|
|
*/
|
|
declare class TouchableHighlightComponent extends React.Component<TouchableHighlightProps> {}
|
|
declare const TouchableHighlightBase: Constructor<NativeMethods> &
|
|
Constructor<TimerMixin> &
|
|
Constructor<TouchableMixin> &
|
|
typeof TouchableHighlightComponent;
|
|
export class TouchableHighlight extends TouchableHighlightBase {}
|