mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
5d26ceaa23
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
69 lines
2.3 KiB
TypeScript
69 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} from '../../../types/private/Utilities';
|
|
import {TimerMixin} from '../../../types/private/TimerMixin';
|
|
import {NativeMethods} from '../../../types/public/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 {}
|