kitten.sh
+1256
-1256
out/llms-full-nativewind.txt
+1256
-1256
out/llms-full-nativewind.txt
···-| `output` | The relative path for the output file. Defaults to `<projectRoot>/node_modules/.cache/nativewind/`. | `<projectRoot>/node_modules/.cache/nativewind/` |-| `inlineRem` | Numeric value for inlining the value of `rem` units on native. Set to `false` to disable this behavior. Defaults to `14`. | `14` |-| `configPath` | Relative path to your `tailwind.config` file. Recommended to use `@config` instead. | `tailwind.config` |-| `hotServerOptions` | Options for the hot server, with a default configuration of `{ port: 8089 }`. | `{ port: 8089 }` |+|`output`|The relative path for the output file. Defaults to `<projectRoot>/node_modules/.cache/nativewind/`.|`<projectRoot>/node_modules/.cache/nativewind/`|+|`inlineRem`|Numeric value for inlining the value of `rem` units on native. Set to `false` to disable this behavior. Defaults to `14`.|`14`|+|`configPath`|Relative path to your `tailwind.config` file. Recommended to use `@config` instead.|`tailwind.config`|+|`hotServerOptions`|Options for the hot server, with a default configuration of `{ port: 8089 }`.|`{ port: 8089 }`|···························The `useColorScheme()` function provides a way to access and manage the device's current color scheme.-| `setColorScheme` | Allows overriding the current color scheme with either `light`, `dark`, or `system`. |+|`setColorScheme`|Allows overriding the current color scheme with either `light`, `dark`, or `system`.|Additionally, you can manually adjust the color scheme using `NativeWindStyleSheet.setColorScheme(colorScheme)`.·····················The following table outlines the support for various background attachment classes in web development:These classes are used to control how a background image is positioned relative to the viewport or its containing element.···The following table outlines various CSS classes related to background clipping, along with their support status:These classes are used to define how the background of an element is clipped, with support limited to web browsers.······The following table outlines various classes used for background images, along with their support status:These classes are specifically designed for use in web development to apply background styles.···The following table outlines the support for different background origin classes in web development:These classes are used to specify the positioning area of a background image within an element. Each class targets a different part of the element's box model:···The following table outlines various CSS classes used for setting background positions, along with their support status:These classes are used to position background images in various locations within an element.···The following table outlines various CSS classes related to background repeat properties, along with their support status:These classes are used to control how background images repeat within an element. Each class is supported exclusively on web platforms.······Both methods utilize the `colorScheme` from Nativewind, which provides a consistent API to interact with React Native's appearance settings. The underlying mechanism involves using the `Appearance` API on native platforms and `prefers-color-scheme` for web environments.························When working with native environments, use `border-0` instead of `border-none` to eliminate borders. Below is a table indicating support levels for various border classes:···············The following table outlines the compatibility of various grid column classes with web platforms:······················································The following table outlines the support status for various background blend mode classes:···················································When using arbitrary styles or defining rotation values in your theme, always specify the `deg` unit. For example: `rotate-[90deg]`.·····················Nativewind offers installation guidance for the two most prevalent React Native bundlers, Metro and Next.js. However, it is compatible with any bundler. To integrate Nativewind successfully, ensure these three conditions are satisfied:-2. React Native should be set up, specifically utilizing React Native Web version 0.17 or higher.-3. The JSX runtime needs to be adjusted to `'automatic'`, and `jsxImportSource` should be assigned to `'nativewind'`.+1. React Native should be set up, specifically utilizing React Native Web version 0.17 or higher.+1. The JSX runtime needs to be adjusted to `'automatic'`, and `jsxImportSource` should be assigned to `'nativewind'`.·········The following table outlines the compatibility of various accent classes with different platforms:···This reformatted content maintains the original structure and intent while ensuring clarity and adherence to markdown formatting standards.···························-| `m-safe` | ✅ Full Support | Applies margins using safe area insets: `margin-top`, `margin-bottom`, `margin-left`, and `margin-right`. |-| `p-safe` | ✅ Full Support | Applies padding using safe area insets: `padding-top`, `padding-bottom`, `padding-left`, and `padding-right`. |-| `*-safe-or-[n]` | ✅ Full Support | Allows substitution of any spacing utility (`*`) and value (`[n]`). Example: `mt-safe-or-4` translates to `margin-top: max(env(safe-area-inset-top), 1rem);`. Another example is `mt-safe-or-[2px]`, resulting in `margin-top: max(env(safe-area-inset-top), 2px);`. |-| `h-screen-safe` | 🌐 Web only | Adjusts height using safe area insets: `height: calc(100vh - (env(safe-area-inset-top) + env(safe-area-inset-bottom)))`. |-| `*-safe-offset-[n]` | 🌐 Web only | Allows substitution of any spacing utility (`*`) and value (`[n]`). Example: `mt-safe-offset-4` results in `margin-top: calc(env(safe-area-inset-top) + 1rem);`. Another example is `mt-safe-offset-[2px]`, resulting in `margin-top: calc(env(safe-area-inset-top) + 2px);`. |+|`m-safe`|✅ Full Support|Applies margins using safe area insets: `margin-top`, `margin-bottom`, `margin-left`, and `margin-right`.|+|`p-safe`|✅ Full Support|Applies padding using safe area insets: `padding-top`, `padding-bottom`, `padding-left`, and `padding-right`.|+|`*-safe-or-[n]`|✅ Full Support|Allows substitution of any spacing utility (`*`) and value (`[n]`). Example: `mt-safe-or-4` translates to `margin-top: max(env(safe-area-inset-top), 1rem);`. Another example is `mt-safe-or-[2px]`, resulting in `margin-top: max(env(safe-area-inset-top), 2px);`.|+|`h-screen-safe`|🌐 Web only|Adjusts height using safe area insets: `height: calc(100vh - (env(safe-area-inset-top) + env(safe-area-inset-bottom)))`.|+|`*-safe-offset-[n]`|🌐 Web only|Allows substitution of any spacing utility (`*`) and value (`[n]`). Example: `mt-safe-offset-4` results in `margin-top: calc(env(safe-area-inset-top) + 1rem);`. Another example is `mt-safe-offset-[2px]`, resulting in `margin-top: calc(env(safe-area-inset-top) + 2px);`.|·········································································································React Native does not support relative line height utilities due to its lack of `em` unit support.······This reformatted content maintains the original structure and information while ensuring clarity and consistency in presentation.·····················
+204
-208
out/llms-full-react-native-gesture-handler.txt
+204
-208
out/llms-full-react-native-gesture-handler.txt
···The `react-native-gesture-handler` library supports the three most recent minor versions of `react-native`. Below is a compatibility table:To fully leverage touch events, ensure you are using `react-native-reanimated` version 2.3.0 or newer.···-| `enabled(value: boolean)` | Indicates whether the handler should analyze touch events. Default is `true`. If set to `false`, the handler's state will never become `ACTIVE`. |-| `shouldCancelWhenOutside(value: boolean)` | When `true`, cancels or fails recognition if a finger leaves the view area. Defaults vary by gesture type; most are `false` except for `LongPressGesture` and `TapGesture`, which default to `true`. |-| `hitSlop(settings)` | Controls the activation area of the gesture within the connected view. Negative numbers reduce bounds evenly, while objects can specify reductions per side or edge. Positive values on Android expand beyond view bounds but not past parent view bounds. Use React Native's View hitSlop for cross-platform support. |-| `cancelsTouchesInView(value)` (**iOS only**) | When `true`, cancels touches for native UI components when active. Default is `true`. |-| `runOnJS(value: boolean)` | Determines if callbacks run on the JS thread (`true`) or UI thread (`false`). Defaults to `false` with `react-native-reanimated`. |-| `simultaneousWithExternalGesture(otherGesture1, otherGesture2, ...)` | Marks gestures for simultaneous recognition without composing them. Requires additional detectors for recognition. |-| `requireExternalGestureToFail(otherGesture1, otherGesture2, ...)` | Adds a relation requiring another gesture to fail before activation. Does not compose gestures; requires additional detectors. |-| `blocksExternalGesture(otherGesture1, otherGesture2, ...)` | Makes other gestures wait until this one fails or doesn't start. Marks relations without composing gestures; requires additional detectors. |-| `activeCursor(value)` (**Web only**) | Specifies the cursor when the gesture activates. Supports CSS cursor values (e.g., `"grab"`, `"zoom-in"`). Default is `"auto"`. |+|`enabled(value: boolean)`|Indicates whether the handler should analyze touch events. Default is `true`. If set to `false`, the handler's state will never become `ACTIVE`.|+|`shouldCancelWhenOutside(value: boolean)`|When `true`, cancels or fails recognition if a finger leaves the view area. Defaults vary by gesture type; most are `false` except for `LongPressGesture` and `TapGesture`, which default to `true`.|+|`hitSlop(settings)`|Controls the activation area of the gesture within the connected view. Negative numbers reduce bounds evenly, while objects can specify reductions per side or edge. Positive values on Android expand beyond view bounds but not past parent view bounds. Use React Native's View hitSlop for cross-platform support.|+|`cancelsTouchesInView(value)` (**iOS only**)|When `true`, cancels touches for native UI components when active. Default is `true`.|+|`runOnJS(value: boolean)`|Determines if callbacks run on the JS thread (`true`) or UI thread (`false`). Defaults to `false` with `react-native-reanimated`.|+|`simultaneousWithExternalGesture(otherGesture1, otherGesture2, ...)`|Marks gestures for simultaneous recognition without composing them. Requires additional detectors for recognition.|+|`requireExternalGestureToFail(otherGesture1, otherGesture2, ...)`|Adds a relation requiring another gesture to fail before activation. Does not compose gestures; requires additional detectors.|+|`blocksExternalGesture(otherGesture1, otherGesture2, ...)`|Makes other gestures wait until this one fails or doesn't start. Marks relations without composing gestures; requires additional detectors.|+|`activeCursor(value)` (**Web only**)|Specifies the cursor when the gesture activates. Supports CSS cursor values (e.g., `"grab"`, `"zoom-in"`). Default is `"auto"`.|···-| `onBegin(callback)` | Called when the gesture handler starts receiving touches but is not yet active. |-| `onStart(callback)` | Called when the gesture is recognized and transitions to an active state. |-| `onEnd(callback)` | Called when a recognized gesture finishes, provided it was previously active. |-| `onFinalize(callback)` | Called when handling finalizes—either recognition completes or fails. |-| `onTouchesCancelled(callback)` | Triggered when a finger stops being tracked, such as when a gesture finishes. |+|`onBegin(callback)`|Called when the gesture handler starts receiving touches but is not yet active.|+|`onStart(callback)`|Called when the gesture is recognized and transitions to an active state.|+|`onEnd(callback)`|Called when a recognized gesture finishes, provided it was previously active.|+|`onFinalize(callback)`|Called when handling finalizes—either recognition completes or fails.|+|`onTouchesCancelled(callback)`|Triggered when a finger stops being tracked, such as when a gesture finishes.|···-| `velocity` | Velocity of the gesture at the current moment, expressed as scale factor per second. |+|`velocity`|Velocity of the gesture at the current moment, expressed as scale factor per second.|-| `pointerType` | Type of pointer device in use, represented by the `PointerType` enum: `TOUCH`, `STYLUS`, `MOUSE`, `KEY`, or `OTHER`. |+|`pointerType`|Type of pointer device in use, represented by the `PointerType` enum: `TOUCH`, `STYLUS`, `MOUSE`, `KEY`, or `OTHER`.|···-| `minForce(value: number)` | Minimal pressure required for activation. Range `[0.0, 1.0]`. Default is `0.2`. |+|`minForce(value: number)`|Minimal pressure required for activation. Range `[0.0, 1.0]`. Default is `0.2`.|-| `enabled(value: boolean)` | Indicates whether the handler analyzes touch events. Default is `true`. |-| `shouldCancelWhenOutside(value: boolean)` | Cancels recognition if finger leaves view area. Defaults vary by handler type. |-| `hitSlop(settings)` | Controls gesture activation area within the view. Supports negative values for reduction. |-| `cancelsTouchesInView(value)` (**iOS only**) | Cancels touches for native UI components when active. Default is `true`. |-| `runOnJS(value: boolean)` | Runs callbacks on JS thread if true, otherwise on the UI thread. Defaults to `false`. |-| `simultaneousWithExternalGesture(otherGesture1, otherGesture2, ...)` | Marks relation for simultaneous recognition with other gestures. |-| `requireExternalGestureToFail(otherGesture1, otherGesture2, ...)` | Requires another gesture to fail before activation. |-| `blocksExternalGesture(otherGesture1, otherGesture2, ...)` | Makes other gestures wait until this one fails or doesn't start. |-| `activeCursor(value)` (**Web only**) | Specifies cursor when gesture activates. Supports CSS cursor values. Default is `"auto"`. |+|`enabled(value: boolean)`|Indicates whether the handler analyzes touch events. Default is `true`.|+|`shouldCancelWhenOutside(value: boolean)`|Cancels recognition if finger leaves view area. Defaults vary by handler type.|+|`hitSlop(settings)`|Controls gesture activation area within the view. Supports negative values for reduction.|+|`cancelsTouchesInView(value)` (**iOS only**)|Cancels touches for native UI components when active. Default is `true`.|+|`runOnJS(value: boolean)`|Runs callbacks on JS thread if true, otherwise on the UI thread. Defaults to `false`.|+|`simultaneousWithExternalGesture(otherGesture1, otherGesture2, ...)`|Marks relation for simultaneous recognition with other gestures.|+|`requireExternalGestureToFail(otherGesture1, otherGesture2, ...)`|Requires another gesture to fail before activation.|+|`blocksExternalGesture(otherGesture1, otherGesture2, ...)`|Makes other gestures wait until this one fails or doesn't start.|+|`activeCursor(value)` (**Web only**)|Specifies cursor when gesture activates. Supports CSS cursor values. Default is `"auto"`.|-| `manualActivation(value: boolean)` | When true, the handler does not activate automatically; state must be manipulated manually. |+|`manualActivation(value: boolean)`|When true, the handler does not activate automatically; state must be manipulated manually.|-| `onStart(callback)` | Called when the gesture is recognized and transitions to active state. |-| `onEnd(callback)` | Called when a recognized gesture finishes, if previously in active state. |-| `onTouchesCancelled(callback)` | Called when a finger stops being tracked, e.g., gesture finishes. |+|`onTouchesCancelled(callback)`|Called when a finger stops being tracked, e.g., gesture finishes.|-| `onChange(callback)` | Called with information about changes in value relative to the last event. |+|`onChange(callback)`|Called with information about changes in value relative to the last event.|-| `state` | Current state of the handler, expressed as one of the constants in the `State` object. |-| `pointerType` | Type of pointer device in use, represented by the `PointerType` enum (`TOUCH`, `STYLUS`, etc.). |+|`state`|Current state of the handler, expressed as one of the constants in the `State` object.|+|`pointerType`|Type of pointer device in use, represented by the `PointerType` enum (`TOUCH`, `STYLUS`, etc.).|···-| `direction(value: Directions)` | Specifies allowed movement directions. Use constants from the `Directions` object, combining multiple directions with \` | `. Example: `fling.direction(Directions.RIGHT | Directions.LEFT);`or`fling.direction(Directions.DOWN);\` |-| `numberOfPointers(value: number)` | Sets the exact number of pointers required for gesture recognition. | | |-| `mouseButton(value: MouseButton)` (Web & Android only) | Chooses which mouse button to respond to, using predefined fields in `MouseButton`: `LEFT`, `RIGHT`, `MIDDLE`, `BUTTON_4`, `BUTTON_5`, `ALL`. Combine with \` | `operator; default is`LEFT\`. | |+|`direction(value: Directions)`|Specifies allowed movement directions. Use constants from the `Directions` object, combining multiple directions with \`|`. Example: `fling.direction(Directions.RIGHT|Directions.LEFT);`or`fling.direction(Directions.DOWN);\`|+|`numberOfPointers(value: number)`|Sets the exact number of pointers required for gesture recognition.|||+|`mouseButton(value: MouseButton)` (Web & Android only)|Chooses which mouse button to respond to, using predefined fields in `MouseButton`: `LEFT`, `RIGHT`, `MIDDLE`, `BUTTON_4`, `BUTTON_5`, `ALL`. Combine with \`|`operator; default is`LEFT\`.||-| `enabled(value: boolean)` | Determines if the handler analyzes touch events. Default is `true`. Disabling during recognition changes state to `FAILED` or `CANCELLED`. |-| `shouldCancelWhenOutside(value: boolean)` | Cancels/fails recognition when a finger leaves the view area. Defaults vary by gesture type; most are `false`, except for `LongPressGesture` and `TapGesture` which default to `true`. |-| `hitSlop(settings)` | Controls the active area for gesture recognition, reducing or expanding bounds as specified. Supports negative numbers, objects with specific side reductions, and `width`/`height` attributes. |-| `cancelsTouchesInView(value)` (**iOS only**) | When `true`, cancels touches for native UI components when active. Default is `true`. |-| `runOnJS(value: boolean)` | Determines if callbacks run on the JS thread (`true`) or UI thread (`false`). Defaults to `false` with `react-native-reanimated`. |-| `simultaneousWithExternalGesture(otherGesture1, otherGesture2, ...)` | Marks gestures for simultaneous recognition without composing them. Requires separate detectors. |-| `requireExternalGestureToFail(otherGesture1, otherGesture2, ...)` | Requires another gesture to fail before activation. Does not compose gestures; requires separate detectors. |-| `blocksExternalGesture(otherGesture1, otherGesture2, ...)` | Delays other gestures until this one fails or doesn't start. Marks relations without composing; requires separate detectors. |+|`enabled(value: boolean)`|Determines if the handler analyzes touch events. Default is `true`. Disabling during recognition changes state to `FAILED` or `CANCELLED`.|+|`shouldCancelWhenOutside(value: boolean)`|Cancels/fails recognition when a finger leaves the view area. Defaults vary by gesture type; most are `false`, except for `LongPressGesture` and `TapGesture` which default to `true`.|+|`hitSlop(settings)`|Controls the active area for gesture recognition, reducing or expanding bounds as specified. Supports negative numbers, objects with specific side reductions, and `width`/`height` attributes.|+|`cancelsTouchesInView(value)` (**iOS only**)|When `true`, cancels touches for native UI components when active. Default is `true`.|+|`runOnJS(value: boolean)`|Determines if callbacks run on the JS thread (`true`) or UI thread (`false`). Defaults to `false` with `react-native-reanimated`.|+|`simultaneousWithExternalGesture(otherGesture1, otherGesture2, ...)`|Marks gestures for simultaneous recognition without composing them. Requires separate detectors.|+|`requireExternalGestureToFail(otherGesture1, otherGesture2, ...)`|Requires another gesture to fail before activation. Does not compose gestures; requires separate detectors.|+|`blocksExternalGesture(otherGesture1, otherGesture2, ...)`|Delays other gestures until this one fails or doesn't start. Marks relations without composing; requires separate detectors.|-| `onBegin(callback)` | Called when the gesture handler starts receiving touches but hasn't yet recognized the gesture. |-| `onStart(callback)` | Triggered when the gesture is recognized and transitions to active state. |-| `onEnd(callback)` | Invoked when a recognized gesture finishes, only if previously active. |-| `onFinalize(callback)` | Called upon finalizing gesture handling—either recognition or failure. |-| `onTouchesCancelled(callback)` | Called when a finger stops being tracked, such as gesture completion. |+|`onBegin(callback)`|Called when the gesture handler starts receiving touches but hasn't yet recognized the gesture.|+|`onStart(callback)`|Triggered when the gesture is recognized and transitions to active state.|+|`onFinalize(callback)`|Called upon finalizing gesture handling—either recognition or failure.|+|`onTouchesCancelled(callback)`|Called when a finger stops being tracked, such as gesture completion.|-| `absoluteX` | X coordinate of the pointer relative to the window, recommended for transformed views. |-| `absoluteY` | Y coordinate of the pointer relative to the window, recommended for transformed views. |+|`absoluteX`|X coordinate of the pointer relative to the window, recommended for transformed views.|+|`absoluteY`|Y coordinate of the pointer relative to the window, recommended for transformed views.|-| `pointerType` | Type of pointer device, using `PointerType`: `TOUCH`, `STYLUS`, `MOUSE`, `KEY`, `OTHER`. |+|`pointerType`|Type of pointer device, using `PointerType`: `TOUCH`, `STYLUS`, `MOUSE`, `KEY`, `OTHER`.|···The `GestureDetector` serves as the core component within RNGH2, tasked with creating and updating native gesture handlers based on the configuration of provided gestures. A key enhancement over previous versions is its ability to recognize multiple gestures simultaneously through gesture composition. It's important to note that `GestureDetector` does not support integration with the Animated API or Reanimated 1.A `Gesture` object facilitates the creation and combination of various gestures, enabling more complex interactions.···The `GestureStateManager` allows manual control over gesture states. Note that react-native-reanimated is required for its use, as it enables synchronous execution of methods within worklets.- **eventType**: Indicates the type of event, such as finger placement on the screen, movement, lifting, or cancellation.···> **Caution**: Do not rely on the order of items in `touches` as it may change during a gesture. Use the `id` attribute to track individual touches across events.- **id**: A unique number representing the touch's ID, used for tracking the touch between events since the ID remains constant while being tracked.···- **absoluteY**: The Y coordinate of the current position of the touch relative to the window, expressed in point units. Recommended for use when the original view can be transformed due to a gesture.The `GestureStateManager` provides manual control over gesture states, requiring `react-native-reanimated` for synchronous execution of methods within worklets.- **Effectiveness**: Ineffective if the handler is currently active or has finished. Activation may be delayed for gestures marked as `exclusive` until a higher-priority gesture fails.- **eventType**: Indicates the type of event, such as finger placement on the screen, movement, lifting, or cancellation.···> **Caution**: Do not rely on the order of items in `touches` as it may change during a gesture. Use the `id` attribute to track individual touches across events.- **id**: A unique number representing the touch's ID, used for tracking the touch between events since the ID remains constant while being tracked.···- **absoluteY**: The Y coordinate of the current position of the touch relative to the window, expressed in point units. Recommended for use when the original view can be transformed due to a gesture.The `GestureStateManager` provides manual control over gesture states, requiring `react-native-reanimated` for synchronous execution of methods within worklets.- **Effectiveness**: Ineffective if the handler is currently active or has finished. Activation may be delayed for gestures marked as `exclusive` until a higher-priority gesture fails.The `GestureDetector` is a key component within RNGH2, tasked with creating and updating native gesture handlers based on the configuration of provided gestures. A notable advancement over previous gesture handlers is its ability to recognize multiple gestures simultaneously through gesture composition. It's important to note that `GestureDetector` does not support the Animated API or Reanimated 1.······-| `children` | Accepts either children or a render function that receives a boolean indicating if the component is currently pressed. |-| `style` | Can be view styles or a function receiving a boolean reflecting the press state and returning view styles. |-| `onLongPress` | Triggered immediately after the pointer has been down for at least `delayLongPress` milliseconds (default: 500 ms). After this, `onPressOut` will be called upon pointer lift and `onPress` won't trigger. |-| `cancelable` | Determines if a press gesture can be interrupted by a parent gesture like scrolling. Defaults to `true`. |-| `delayHoverOut` (Web only) | Duration to wait after hover out before calling `onHoverOut`. |-| `hitSlop` (Android & iOS only) | Additional distance outside of the view where a press is detected and `onPressIn` is triggered. Accepts `number` or `Rect`. |-| `pressRetentionOffset` (Android & iOS only) | Extra distance outside of the view (or `hitSlop` if present) to consider a touch as a press before `onPressOut` is triggered. Accepts `number` or `Rect`. |-| `android_ripple` (Android only) | Enables the Android ripple effect and configures its color, radius, etc. Accepts `RippleConfig`. |-| `testOnly_pressed` | Used for documentation or testing purposes (e.g., snapshot testing). |-| `unstable_pressDelay` | Duration in milliseconds to wait after press down before calling `onPressIn`. |+|`children`|Accepts either children or a render function that receives a boolean indicating if the component is currently pressed.|+|`style`|Can be view styles or a function receiving a boolean reflecting the press state and returning view styles.|+|`onLongPress`|Triggered immediately after the pointer has been down for at least `delayLongPress` milliseconds (default: 500 ms). After this, `onPressOut` will be called upon pointer lift and `onPress` won't trigger.|+|`cancelable`|Determines if a press gesture can be interrupted by a parent gesture like scrolling. Defaults to `true`.|+|`hitSlop` (Android & iOS only)|Additional distance outside of the view where a press is detected and `onPressIn` is triggered. Accepts `number` or `Rect`.|+|`pressRetentionOffset` (Android & iOS only)|Extra distance outside of the view (or `hitSlop` if present) to consider a touch as a press before `onPressOut` is triggered. Accepts `number` or `Rect`.|+|`android_ripple` (Android only)|Enables the Android ripple effect and configures its color, radius, etc. Accepts `RippleConfig`.|+|`unstable_pressDelay`|Duration in milliseconds to wait after press down before calling `onPressIn`.|···- **`BACK`**: Drawer appears below the content view, revealed by sliding away the content view.···-| `friction` | A number specifying the delay in visual interaction relative to gesture distance. E.g., `1` means no delay, `2` doubles it. |-| `leftThreshold` | Distance from the left edge for panel animation to open or close state. Defaults to half of the panel's width. |-| `rightThreshold` | Distance from the right edge for panel animation to open or close state. Defaults to half of the panel's width. |-| `dragOffsetFromLeftEdge` | Minimum drag distance from the left edge to consider a swipe (default: 10). |-| `dragOffsetFromRightEdge` | Minimum drag distance from the right edge to consider a swipe (default: 10). |-| `overshootLeft` | Boolean indicating if swiping beyond the left action panel's width is allowed. Defaults to `true` if `renderLeftActions` is provided. |-| `overshootRight` | Boolean indicating if swiping beyond the right action panel's width is allowed. Defaults to `true` if `renderRightActions` is provided. |-| `overshootFriction` | Number specifying delay in visual interaction at overshoot (default: 1). For a native feel, try `8` or above. |+|`friction`|A number specifying the delay in visual interaction relative to gesture distance. E.g., `1` means no delay, `2` doubles it.|+|`leftThreshold`|Distance from the left edge for panel animation to open or close state. Defaults to half of the panel's width.|+|`rightThreshold`|Distance from the right edge for panel animation to open or close state. Defaults to half of the panel's width.|+|`dragOffsetFromLeftEdge`|Minimum drag distance from the left edge to consider a swipe (default: 10).|+|`dragOffsetFromRightEdge`|Minimum drag distance from the right edge to consider a swipe (default: 10).|+|`overshootLeft`|Boolean indicating if swiping beyond the left action panel's width is allowed. Defaults to `true` if `renderLeftActions` is provided.|+|`overshootRight`|Boolean indicating if swiping beyond the right action panel's width is allowed. Defaults to `true` if `renderRightActions` is provided.|+|`overshootFriction`|Number specifying delay in visual interaction at overshoot (default: 1). For a native feel, try `8` or above.|···-| `friction` | A number specifying how much the visual interaction will be delayed compared to the gesture distance. For example, a value of `1` means the swipeable panel follows the gesture exactly; `2` makes it two times "slower". |-| `leftThreshold` | Distance from the left edge at which the released panel animates to the open state (or vice versa). Default is half of the panel's width. |-| `rightThreshold` | Distance from the right edge for similar behavior as `leftThreshold`. Default is also half of the panel's width. |-| `dragOffsetFromLeftEdge` | Minimum distance that must be dragged from the left edge to consider it a swipe. Default value: `10`. |-| `dragOffsetFromRightEdge` | Similar to `dragOffsetFromLeftEdge`, but for the right edge. Default value: `10`. |-| `overshootLeft` | Boolean indicating if the panel can be pulled further than the left actions panel's width. Defaults to `true` if a left panel render method is present. |-| `overshootRight` | Similar to `overshootLeft`, but for the right side. Defaults to `true` if a right panel render method is present. |-| `overshootFriction` | Number specifying visual interaction delay at overshoot. Default value: `1`. For a native feel, try `8` or above. |+|`friction`|A number specifying how much the visual interaction will be delayed compared to the gesture distance. For example, a value of `1` means the swipeable panel follows the gesture exactly; `2` makes it two times "slower".|+|`leftThreshold`|Distance from the left edge at which the released panel animates to the open state (or vice versa). Default is half of the panel's width.|+|`rightThreshold`|Distance from the right edge for similar behavior as `leftThreshold`. Default is also half of the panel's width.|+|`dragOffsetFromLeftEdge`|Minimum distance that must be dragged from the left edge to consider it a swipe. Default value: `10`.|+|`dragOffsetFromRightEdge`|Similar to `dragOffsetFromLeftEdge`, but for the right edge. Default value: `10`.|+|`overshootLeft`|Boolean indicating if the panel can be pulled further than the left actions panel's width. Defaults to `true` if a left panel render method is present.|+|`overshootRight`|Similar to `overshootLeft`, but for the right side. Defaults to `true` if a right panel render method is present.|+|`overshootFriction`|Number specifying visual interaction delay at overshoot. Default value: `1`. For a native feel, try `8` or above.|-| `onSwipeableOpen` | Called when an action panel gets open (either right or left). Takes swipe direction as an argument. |-| `onSwipeableClose` | Called when the action panel is closed, with swipe direction as an argument. |-| `onSwipeableWillOpen` | Called when an action panel starts animating on open (either right or left), taking swipe direction as an argument. |-| `onSwipeableWillClose` | Called when an action panel starts animating on close, with swipe direction as an argument. |+|`onSwipeableOpen`|Called when an action panel gets open (either right or left). Takes swipe direction as an argument.|+|`onSwipeableClose`|Called when the action panel is closed, with swipe direction as an argument.|+|`onSwipeableWillOpen`|Called when an action panel starts animating on open (either right or left), taking swipe direction as an argument.|+|`onSwipeableWillClose`|Called when an action panel starts animating on close, with swipe direction as an argument.|···
+307
-307
out/llms-full-react-native-reanimated.txt
+307
-307
out/llms-full-react-native-reanimated.txt
·········This overview provides a concise guide to using the `useEvent` hook effectively within React Native Reanimated projects.···This documentation provides a comprehensive overview of how to utilize the `useHandler` hook within React Native Reanimated for creating custom event handlers.··················- On the Web, it is necessary to pass the returned handler object to both `onGestureEvent` and `onHandlerStateChange` parameters.························-- **`reduceMotion`** _(Optional)_: Determines how the animation responds to the device's reduced motion accessibility setting.+- **`reduceMotion`** *(Optional)*: Determines how the animation responds to the device's reduced motion accessibility setting.······-| height | `SharedValue<number>` | A shared value representing the current height of the keyboard. |-| state | `SharedValue<KeyboardState>` | A shared value indicating the current state of the keyboard. Possible states: `{ CLOSED, OPEN, CLOSING, OPENING }` |+|height|`SharedValue<number>`|A shared value representing the current height of the keyboard.|+|state|`SharedValue<KeyboardState>`|A shared value indicating the current state of the keyboard. Possible states: `{ CLOSED, OPEN, CLOSING, OPENING }`|···············`withClamp` returns an animation object. This can be directly assigned to a shared value or used as a style value in `useAnimatedStyle`.···-| interval | `number \| "auto"` | `"auto"` | Time between sensor readings in milliseconds. `"auto"` matches the device's screen refresh rate. |-| adjustToInterfaceOrientation | `boolean` | `true` | Adjusts measurements to the current interface orientation. |-| iosReferenceFrame | `IOSReferenceFrame` | `IOSReferenceFrame.Auto` | Frame of reference for iOS sensors. |+|interval|`number \| "auto"`|`"auto"`|Time between sensor readings in milliseconds. `"auto"` matches the device's screen refresh rate.|+|adjustToInterfaceOrientation|`boolean`|`true`|Adjusts measurements to the current interface orientation.|+|iosReferenceFrame|`IOSReferenceFrame`|`IOSReferenceFrame.Auto`|Frame of reference for iOS sensors.|···-| sensor | `SharedValue<Value3D \| ValueRotation>` | Shared value with sensor measurements. |············-**Info:** The term _mutable value_ refers to an object created by `makeMutable`, distinguishing it from a _shared value_, which is essentially a mutable value with automatic cleanup.+**Info:** The term *mutable value* refers to an object created by `makeMutable`, distinguishing it from a *shared value*, which is essentially a mutable value with automatic cleanup.- Avoid invoking `makeMutable` directly within component scope. Component re-renders will generate a new object, potentially resetting the initial value and losing previous state.···-| Object Creation | Creates a new object on each call | Reuses the same object on each call |-| Initial Value Change | A new object is created if `initial` changes | The initially created object remains unchanged if `initialValue` changes |-| Scope Usage | Can be used outside of component scope | Limited to use within component scope |-| Loop Usage | Usable in loops with variable iterations | Usable in loops only if the number of hooks (`useSharedValue` calls) is constant |-| Animation Cancellation | Does not automatically cancel animations on unmount | Automatically cancels animations when the component unmounts |+|Initial Value Change|A new object is created if `initial` changes|The initially created object remains unchanged if `initialValue` changes|+|Loop Usage|Usable in loops with variable iterations|Usable in loops only if the number of hooks (`useSharedValue` calls) is constant|+|Animation Cancellation|Does not automatically cancel animations on unmount|Automatically cancels animations when the component unmounts|···-| **Cause** | Call stacks often highlight Reanimated's internal code rather than API misuse. |Understanding this behavior is crucial for effectively diagnosing and resolving issues within Reanimated projects.······The example below illustrates the difference in call stacks before and after applying the Reanimated Metro config wrapper. The **Before** scenario shows Reanimated source code as the error origin, while the **After** scenario reveals the actual incorrect code that caused the error.- `wrapWithReanimatedMetroConfig` does not remove any stack frames; it only collapses irrelevant ones from Reanimated. To inspect these, you can expand collapsed stack frames by clicking on the **See N more frames** text at the bottom of the **Call Stack**.- Some errors, especially those arising from asynchronous code, may still point to Reanimated internals instead of the exact problematic line in your code. This happens because stack traces can lose track of the original code that initiated the asynchronous operation. In such cases, manual debugging based on the error message is necessary to identify the potential cause of the problem.······- **Expo Prebuild or React Native without Framework**: Use a version compatible with your React Native version according to the Compatibility table.···-| Version | 0.63 | 0.64 | 0.65 | 0.66 | 0.67 | 0.68 | 0.69 | 0.70 | 0.71 | 0.72 | 0.73 | 0.74 | 0.75 | 0.76 | 0.77 | 0.78 | 0.79 | 0.80 |-| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |-| 3.18.0 | no | no | no | no | no | no | no | no | no | no | no | no | yes | yes | yes | yes | yes | yes |-| 3.17.4 - 3.17.5 | no | no | no | no | no | no | no | no | no | no | no | no | yes | yes | yes | yes | yes | no |-| 3.17.1 – 3.17.3 | no | no | no | no | no | no | no | no | no | no | no | no | yes | yes | yes | yes | no | no |-| 3.17.0 | no | no | no | no | no | no | no | no | no | no | no | no | yes | yes | yes | no | no | no |-| 3.16.7 | no | no | no | no | no | no | no | no | no | no | no | yes | yes | yes | yes | no | no | no |-| 3.16.0 – 3.16.6 | no | no | no | no | no | no | no | no | no | no | no | yes | yes | yes | no | no | no | no |-| 3.15.x | no | no | no | no | no | no | no | no | no | no | no | yes | yes | no | no | no | no | no |-| 3.9.x – 3.14.x | no | no | no | no | no | no | no | no | no | no | no | yes | no | no | no | no | no | no |-| 3.6.x – 3.8.x | no | no | no | yes | yes | yes | yes | yes | yes | yes | yes | no | no | no | no | no | no | no |-| 3.5.x | no | no | no | yes | yes | yes | yes | yes | yes | yes | no | no | no | no | no | no | no | no |-| 3.3.x – 3.4.x | yes | yes | yes | yes | yes | yes | yes | yes | yes | yes | no | no | no | no | no | no | no | no |-| 3.0.x – 3.2.x | yes | yes | yes | yes | yes | yes | yes | yes | yes | no | no | no | no | no | no | no | no | no |-| 2.14.x – 2.17.x | yes | yes | yes | yes | yes | yes | yes | yes | yes | no | no | no | no | no | no | no | no | no |-| 2.11.x – 2.13.x | yes | yes | yes | yes | yes | yes | yes | yes | no | no | no | no | no | no | no | no | no | no |-| 2.10.x | yes | yes | yes | yes | yes | yes | yes | no | no | no | no | no | no | no | no | no | no | no |-| 2.5.x – 2.9.x | yes | yes | yes | yes | yes | yes | no | no | no | no | no | no | no | no | no | no | no | no |-| 2.3.x – 2.4.x | yes | yes | yes | yes | yes | no | no | no | no | no | no | no | no | no | no | no | no | no |+|Version|0.63|0.64|0.65|0.66|0.67|0.68|0.69|0.70|0.71|0.72|0.73|0.74|0.75|0.76|0.77|0.78|0.79|0.80|**Note:** Reanimated 2 will not receive support for the newest React Native versions. To access the latest features and updates, upgrade to Reanimated 3.···-| Version | 0.63 | 0.64 | 0.65 | 0.66 | 0.67 | 0.68 | 0.69 | 0.70 | 0.71 | 0.72 | 0.73 | 0.74 | 0.75 | 0.76 | 0.77 | 0.78 | 0.79 | 0.80 |-| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |-| 3.18.0 | no | no | no | no | no | no | no | no | no | no | no | no | yes | yes | yes | yes | yes | yes |-| 3.17.4 - 3.17.5 | no | no | no | no | no | no | no | no | no | no | no | no | yes | yes | yes | yes | yes | no |-| 3.17.1 – 3.17.3 | no | no | no | no | no | no | no | no | no | no | no | no | yes | yes | yes | yes | no | no |-| 3.17.0 | no | no | no | no | no | no | no | no | no | no | no | no | yes | yes | yes | no | no | no |-| 3.16.7 | no | no | no | no | no | no | no | no | no | no | no | yes | yes | yes | yes | no | no | no |-| 3.16.0 – 3.16.6 | no | no | no | no | no | no | no | no | no | no | no | yes | yes | yes | no | no | no | no |-| 3.15.x | no | no | no | no | no | no | no | no | no | no | no | yes | yes | no | no | no | no | no |-| 3.9.x – 3.14.x | no | no | no | no | no | no | no | no | no | no | no | yes | no | no | no | no | no | no |-| 3.6.x – 3.8.x | no | no | no | no | no | no | no | no | no | yes | yes | no | no | no | no | no | no | no |-| 3.1.x – 3.5.x | no | no | no | no | no | no | no | no | no | yes | no | no | no | no | no | no | no | no |-| 3.0.x | no | no | no | no | no | no | no | no | yes | no | no | no | no | no | no | no | no | no |+|Version|0.63|0.64|0.65|0.66|0.67|0.68|0.69|0.70|0.71|0.72|0.73|0.74|0.75|0.76|0.77|0.78|0.79|0.80|······This table indicates that all predefined transitions are compatible across Android, iOS, and web platforms.···¹ - Functions use web implementations, running worklets on the JS thread. Measure and Layout Animations are unavailable. ² - Experimental feature.···**Summary:** Functions use web implementations, running on the JS thread. Measure and Layout Animations are unavailable.**Summary:** Available only on iOS devices with the JSC engine. Worklet debugging is supported.···- **Known Issues:** Include reload failures, breakpoint issues on iOS, unresponsive consoles without animations, and more. These do not affect release builds or debug builds where the debugger is disconnected during a reload.-_Efforts are ongoing to enhance debugging experiences with Chrome DevTools and Flipper on Hermes._+*Efforts are ongoing to enhance debugging experiences with Chrome DevTools and Flipper on Hermes.*···-The _Fundamentals_ section aims to establish a solid understanding of the core concepts of Reanimated, empowering you to explore more complex scenarios independently. This section includes interactive examples, code snippets, and detailed explanations.+The *Fundamentals* section aims to establish a solid understanding of the core concepts of Reanimated, empowering you to explore more complex scenarios independently. This section includes interactive examples, code snippets, and detailed explanations.···············-| easing | `Easing` | `Easing.inOut(Easing.quad)` | An easing function defining the animation curve. |-| reduceMotion | `ReduceMotion` | `ReduceMotion.System` | Determines how the animation responds to reduced motion settings on devices. |+|easing|`Easing`|`Easing.inOut(Easing.quad)`|An easing function defining the animation curve.|+|reduceMotion|`ReduceMotion`|`ReduceMotion.System`|Determines how the animation responds to reduced motion settings on devices.|···-The _Fundamentals_ section aims to establish a solid understanding of the core concepts of Reanimated, empowering you to explore more complex scenarios independently. This section includes interactive examples, code snippets, and detailed explanations.+The *Fundamentals* section aims to establish a solid understanding of the core concepts of Reanimated, empowering you to explore more complex scenarios independently. This section includes interactive examples, code snippets, and detailed explanations.······Unlike `withTiming`, `withSpring` is physics-based and simulates real-world spring dynamics, making animations appear more realistic.-When adjusting springs, focus on these three properties: `mass`, `stiffness` (also known as _tension_), and `damping` (also known as _friction_).+When adjusting springs, focus on these three properties: `mass`, `stiffness` (also known as *tension*), and `damping` (also known as *friction*).···-| mass (optional) | `number` | 1 | The weight of the spring. Lower values make the animation faster. |-| damping (optional) | `number` | 10 | Controls how quickly a spring slows down; higher values result in quicker rest. |+|mass (optional)|`number`|1|The weight of the spring. Lower values make the animation faster.|+|damping (optional)|`number`|10|Controls how quickly a spring slows down; higher values result in quicker rest.|-| duration (optional) | `number` | 2000 | Length of the animation in milliseconds. Available in Reanimated ≥ 3.2.x. |-| dampingRatio (optional) | `number` | 0.5 | Determines how damped the spring is; `1` means critically damped, and values >1 mean overdamped. Available in Reanimated ≥ 3.2.x. |+|duration (optional)|`number`|2000|Length of the animation in milliseconds. Available in Reanimated ≥ 3.2.x.|+|dampingRatio (optional)|`number`|0.5|Determines how damped the spring is; `1` means critically damped, and values >1 mean overdamped. Available in Reanimated ≥ 3.2.x.|**Note**: The `mass` and `damping` properties cannot be used simultaneously with `duration` and `dampingRatio`. When both are provided, `duration` and `dampingRatio` take precedence.-| overshootClamping (optional) | `boolean` | false | Prevents the spring from bouncing over the `toValue`. |-| restDisplacementThreshold (optional) | `number` | 0.01 | Displacement below which the spring will settle at `toValue`. |-| restSpeedThreshold (optional) | `number` | 2 | Speed threshold in pixels per second for settling at `toValue`. |-| reduceMotion (optional) | `ReduceMotion` | `ReduceMotion.System` | Determines animation response to reduced motion settings. Available in Reanimated ≥ 3.5.x. |-| clamp (optional) | `[number, number]` | `undefined` | Limits the movement scope; reduces bounciness if exceeded. Available in Reanimated ≥ 3.6.x. |+|overshootClamping (optional)|`boolean`|false|Prevents the spring from bouncing over the `toValue`.|+|restDisplacementThreshold (optional)|`number`|0.01|Displacement below which the spring will settle at `toValue`.|+|restSpeedThreshold (optional)|`number`|2|Speed threshold in pixels per second for settling at `toValue`.|+|reduceMotion (optional)|`ReduceMotion`|`ReduceMotion.System`|Determines animation response to reduced motion settings. Available in Reanimated ≥ 3.5.x.|+|clamp (optional)|`[number, number]`|`undefined`|Limits the movement scope; reduces bounciness if exceeded. Available in Reanimated ≥ 3.6.x.|··················-| `deceleration` (optional) | `number` | 0.998 | Rate at which the velocity decreases over time. |-| `clamp` (optional)\* | `[number, number]` | \[] | Array specifying bounds to restrict the animation's range. The animation stops when either bound is reached unless `rubberBandEffect` is set to `true`. \*Required if `rubberBandEffect` is enabled. |-| `rubberBandEffect` (optional) | `boolean` | false | Enables bouncing over the limit specified in `clamp`. |-| `rubberBandFactor` (optional) | `number` | 0.6 | Determines the strength of the rubber band effect. |-| `reduceMotion` (optional) | `ReduceMotion` | `ReduceMotion.System` | Controls how the animation responds to the device's reduced motion accessibility setting. |+|`clamp` (optional)\*|`[number, number]`|\[]|Array specifying bounds to restrict the animation's range. The animation stops when either bound is reached unless `rubberBandEffect` is set to `true`. \*Required if `rubberBandEffect` is enabled.|+|`rubberBandEffect` (optional)|`boolean`|false|Enables bouncing over the limit specified in `clamp`.|+|`rubberBandFactor` (optional)|`number`|0.6|Determines the strength of the rubber band effect.|+|`reduceMotion` (optional)|`ReduceMotion`|`ReduceMotion.System`|Controls how the animation responds to the device's reduced motion accessibility setting.|···························- **`output`**: An array of color strings (e.g., `'red'`, `'#ff0000'`, `'rgba(255, 0, 0, 0.5)'`) that define the output colors. It must have at least as many points as the input range.-- **`colorSpace`** _(Optional)_: Specifies the color space for interpolation, either `'HSV'` or `'RGB'`. Defaults to `'RGB'`.+- **`colorSpace`** *(Optional)*: Specifies the color space for interpolation, either `'HSV'` or `'RGB'`. Defaults to `'RGB'`.-| `useCorrectedHSVInterpolation` | `boolean` | true | Reduces the number of hues during interpolation by treating HSV as circular. |+|`useCorrectedHSVInterpolation`|`boolean`|true|Reduces the number of hues during interpolation by treating HSV as circular.|···
+737
-737
out/llms-full-react-native.txt
+737
-737
out/llms-full-react-native.txt
···Menu paths are presented in bold and utilize carets for navigating submenus. Example: **Android Studio > Preferences**With an understanding of how to navigate these guides, it's time to explore the foundation of React Native: Native Components.······-| **`onPress`** | Handler called when the user taps the button. | `({nativeEvent: PressEvent})` | Yes |-| **`title`** | Text displayed inside the button. On Android, this title is converted to uppercase. | string | Yes |-| `accessibilityLanguage` | Language used by screen readers on iOS, following BCP 47 specification. | string | No |-| `accessibilityActions` | List of actions for assistive technologies to invoke programmatically. | array | No |-| `onAccessibilityAction` | Invoked when an accessibility action is performed by the user. | function | No |-| `nextFocusDown` | Next view to receive focus when navigating down on Android TV. | number | No |-| `nextFocusForward` | Next view to receive focus when navigating forward on Android TV. | number | No |-| `nextFocusLeft` | Next view to receive focus when navigating left on Android TV. | number | No |-| `nextFocusRight` | Next view to receive focus when navigating right on Android TV. | number | No |-| `nextFocusUp` | Next view to receive focus when navigating up on Android TV. | number | No |-| `touchSoundDisabled` | Disables system sound on touch if set to true (Android only). | boolean | No |+|**`onPress`**|Handler called when the user taps the button.|`({nativeEvent: PressEvent})`|Yes|+|**`title`**|Text displayed inside the button. On Android, this title is converted to uppercase.|string|Yes|+|`accessibilityLanguage`|Language used by screen readers on iOS, following BCP 47 specification.|string|No|+|`accessibilityActions`|List of actions for assistive technologies to invoke programmatically.|array|No|+|`onAccessibilityAction`|Invoked when an accessibility action is performed by the user.|function|No|+|`nextFocusForward`|Next view to receive focus when navigating forward on Android TV.|number|No|+|`touchSoundDisabled`|Disables system sound on touch if set to true (Android only).|boolean|No|This table summarizes the properties available for the Button component, detailing their purpose and default values where applicable.···The `config` object provides enhanced versions of all responder callbacks, including the `PanResponder` gesture state. Replace `onResponder*` with `onPanResponder*`. For example:······-_Example section would typically include a demonstration of how to implement the `<ImageBackground>` component._+*Example section would typically include a demonstration of how to implement the `<ImageBackground>` component.*-_Reference section would provide additional resources or links for further information about the `<ImageBackground>` component._+*Reference section would provide additional resources or links for further information about the `<ImageBackground>` component.*······Defines how the view should respond to the presence of the keyboard. Note that Android and iOS handle this prop differently, but setting `behavior` is recommended for both platforms.Specifies the style applied to the content container (View) when the behavior is set to `'position'`.Represents the distance between the top of the user's screen and the React Native view. This value may be non-zero in certain scenarios.·········Sets the background color of the modal's container. Defaults to `white` unless `transparent` is set to `true`.Decides whether the modal appears under the system navigation bar. Requires `statusBarTranslucent` to also be `true`.Triggered when the orientation changes while the modal is displayed. The callback provides 'portrait' or 'landscape'. It also fires on initial render, regardless of current orientation.Invoked when the user presses the hardware back button on Android or the menu button on Apple TV. Note that `BackHandler` events are suppressed while the modal is open. On iOS, it's called during a drag gesture dismissal with `presentationStyle` set to `pageSheet` or `formSheet`.···-| enum(`'fullScreen'`, `'pageSheet'`, `'formSheet'`, `'overFullScreen'`) | `fullScreen` if `transparent={false}`\*\*\*`overFullScreen` if `transparent={true}` |+|enum(`'fullScreen'`, `'pageSheet'`, `'formSheet'`, `'overFullScreen'`)|`fullScreen` if `transparent={false}`\*\*\*`overFullScreen` if `transparent={true}`|···-| array of enums(`'portrait'`, `'portrait-upside-down'`, `'landscape'`, `'landscape-left'`, `'landscape-right'`) | `['portrait']` |+|array of enums(`'portrait'`, `'portrait-upside-down'`, `'landscape'`, `'landscape-left'`, `'landscape-right'`)|`['portrait']`|To integrate React Native into an existing iOS application, follow these steps carefully. This guide assumes you have a basic understanding of both iOS development using Xcode and JavaScript/React Native.···-| foreground | boolean | No | If true, adds the ripple effect to the view's foreground instead of the background. Useful when child views have their own backgrounds or images are displayed, preventing the ripple from being obscured. |+|foreground|boolean|No|If true, adds the ripple effect to the view's foreground instead of the background. Useful when child views have their own backgrounds or images are displayed, preventing the ripple from being obscured.|···Support for TV devices, specifically Apple TV and Android TV, was integrated into React Native applications with the goal of enabling these apps to function on such platforms with minimal modifications required in their JavaScript code.-> **Deprecated Notice:** The support for TV devices has been transitioned to a separate repository named "React Native for TV." For detailed guidance on projects targeting Apple TV or Android TV, please refer to the _README_ file within that repository.+> **Deprecated Notice:** The support for TV devices has been transitioned to a separate repository named "React Native for TV." For detailed guidance on projects targeting Apple TV or Android TV, please refer to the *README* file within that repository.The provided documentation outlines various properties and methods associated with a ScrollView component, likely from a mobile development framework such as React Native. Below is a summary of the key features:···-| `animated` | boolean | No | `false` | Determines if transitions between status bar property changes should be animated. Supported for `backgroundColor`, `barStyle`, and `hidden`. |-| `backgroundColor` (Android) | color | No | Default system StatusBar background color or `'black'` if not defined | The background color of the status bar. **Warning:** Deprecated in API level 35 due to edge-to-edge enforcement introduced in Android 15. |-| `barStyle` | StatusBarStyle | No | `'default'` | Sets the color of the status bar text. On Android, this affects only API versions 23 and above. |-| `networkActivityIndicatorVisible` (iOS) | boolean | No | `false` | Controls visibility of the network activity indicator. |-| `showHideTransition` (iOS) | StatusBarAnimation | No | `'fade'` | The transition effect when showing or hiding the status bar using the `hidden` prop. |-| `translucent` (Android) | boolean | No | `false` | Determines if the status bar is translucent, allowing the app to draw under it. Useful with a semi-transparent status bar color. |+|`animated`|boolean|No|`false`|Determines if transitions between status bar property changes should be animated. Supported for `backgroundColor`, `barStyle`, and `hidden`.|+|`backgroundColor` (Android)|color|No|Default system StatusBar background color or `'black'` if not defined|The background color of the status bar. **Warning:** Deprecated in API level 35 due to edge-to-edge enforcement introduced in Android 15.|+|`barStyle`|StatusBarStyle|No|`'default'`|Sets the color of the status bar text. On Android, this affects only API versions 23 and above.|+|`networkActivityIndicatorVisible` (iOS)|boolean|No|`false`|Controls visibility of the network activity indicator.|+|`showHideTransition` (iOS)|StatusBarAnimation|No|`'fade'`|The transition effect when showing or hiding the status bar using the `hidden` prop.|+|`translucent` (Android)|boolean|No|`false`|Determines if the status bar is translucent, allowing the app to draw under it. Useful with a semi-transparent status bar color.|···-| **props (Required)** | any | Object containing the `StatusBar` props for the replacement stack entry. |+|**props (Required)**|any|Object containing the `StatusBar` props for the replacement stack entry.|·········-| animation (iOS) | StatusBarAnimation | Animation when changing the hidden property of the status bar. |+|animation (iOS)|StatusBarAnimation|Animation when changing the hidden property of the status bar.|·········-- _iOS_: When the switch is off (`false`), the track contracts into its border. To modify the color of the background revealed by this contracted track, use `ios_backgroundColor`.+- *iOS*: When the switch is off (`false`), the track contracts into its border. To modify the color of the background revealed by this contracted track, use `ios_backgroundColor`.···-| `activeOpacity` | Sets the opacity of the wrapped view during touch interaction. Must be between 0 and 1. Defaults to 0.85. Requires `underlayColor`. | number |+|`activeOpacity`|Sets the opacity of the wrapped view during touch interaction. Must be between 0 and 1. Defaults to 0.85. Requires `underlayColor`.|number|-- **hasTVPreferredFocus**: _(Apple TV only)_ Indicates TV preferred focus (refer to the View component documentation).+- **hasTVPreferredFocus**: *(Apple TV only)* Indicates TV preferred focus (refer to the View component documentation).······-| `accessibilityIgnoresInvertColors` (iOS) | Indicates whether the view should be inverted when color inversion is enabled. A value of `true` prevents inversion even if color inversion is turned on. See the Accessibility guide for more information. | Boolean |-| `accessible` | When set to `true`, marks the view as an accessibility element. By default, all touchable elements are accessible. | bool |-| `accessibilityLabel` | Overrides the text read by screen readers when interacting with the element. By default, it is constructed from all child `Text` nodes separated by spaces. | string |-| `accessibilityLanguage` (iOS) | Specifies the language used by the screen reader for this element, following the BCP 47 specification. See the iOS `accessibilityLanguage` documentation for more information. | string |-| `accessibilityHint` | Provides a hint to help users understand what will happen when they perform an action on the accessibility element if it's not clear from the label. | string |-| `accessibilityRole` | Communicates the purpose of a component to assistive technology users. Possible values include `'none'`, `'button'`, `'link'`, `'search'`, `'image'`, `'keyboardkey'`, `'text'`, `'adjustable'`, and more. | string |-| `accessibilityState` | Describes the current state of a component to assistive technology users. See the Accessibility guide for more information. | object: `{disabled, selected, checked, busy, expanded}` |-| `accessibilityActions` | Allows assistive technologies to programmatically invoke actions on a component. Each action should include a name and label. See the Accessibility guide for more details. | array |-| `aria-busy` | Indicates that an element is being modified and assistive technologies may want to wait until changes are complete before notifying the user. | boolean |-| `aria-checked` | Represents the state of a checkable element, which can be either a boolean or `'mixed'`. | boolean, 'mixed' |-| `aria-disabled` | Indicates that an element is perceivable but disabled and not editable or operable. | boolean |-| `aria-expanded` | Shows whether an expandable element is currently expanded or collapsed. | boolean |-| `aria-hidden` | Specifies if the accessibility elements within this element are hidden, affecting how assistive technologies like VoiceOver interact with sibling views. | boolean |-| `aria-live` (Android) | Indicates updates to an element and describes the types of updates expected by user agents, assistive technologies, and users. Options include `'assertive'`, `'off'`, and `'polite'`. | enum: `'assertive'`, `'off'`, `'polite'` |-| `aria-modal` (iOS) | Boolean indicating whether VoiceOver should ignore sibling elements within views. Takes precedence over the `accessibilityViewIsModal` prop. | boolean |-| `onAccessibilityAction` | Invoked when an accessibility action is performed by the user. The function receives an event containing the name of the action to perform. See the Accessibility guide for more information. | function |-| `accessibilityValue` | Represents a component's current value, either as a textual description or range information (min, max, now) for components like sliders and progress bars. | object: `{min, max, now, text}` |-| `aria-valuemax` | Specifies the maximum value for range-based components, taking precedence over the `max` value in the `accessibilityValue` prop. | number |-| `aria-valuemin` | Specifies the minimum value for range-based components, taking precedence over the `min` value in the `accessibilityValue` prop. | number |-| `aria-valuenow` | Represents the current value for range-based components, taking precedence over the `now` value in the `accessibilityValue` prop. | number |-| `aria-valuetext` | Provides a textual description of the component's value, taking precedence over the `text` value in the `accessibilityValue` prop. | string |-| `delayLongPress` | Duration (in milliseconds) from `onPressIn` before `onLongPress` is called. | number |-| `delayPressIn` | Duration (in milliseconds) from the start of a touch until `onPressIn` is invoked. | number |-| `delayPressOut` | Duration (in milliseconds) after releasing a touch before `onPressOut` is called. | number |-| `hitSlop` | Defines how far from the button a touch can start. This value is added to `pressRetentionOffset` when moving off of the button. The touch area does not extend past parent view bounds and sibling views with higher Z-index take precedence if overlapping. | Rect or number |-| `id` | Used to locate this view from native code, taking precedence over the `nativeID` prop. | string |-| `onLayout` | Called on mount and during layout changes. | `({nativeEvent: LayoutEvent}) => void` |-| `onLongPress` | Triggered if the time after `onPressIn` exceeds 370 milliseconds, customizable with `delayLongPress`. | function |-| `onPress` | Called when a touch is released unless cancelled (e.g., by a scroll that steals the responder lock). The first argument is an event in form of PressEvent. | function |-| `onPressIn` | Invoked as soon as the touchable element is pressed, even before `onPress`. Useful for tasks like network requests. The first argument is an event in form of PressEvent. | function |-| `onPressOut` | Called immediately after a touch is released, prior to `onPress`. The first argument is an event in form of PressEvent. | function |-| `pressRetentionOffset` | Defines how far a touch may move off the button before deactivating it when the scroll view is disabled. Re-activation occurs upon moving back over the button. Pass a constant to reduce memory allocations. | Rect or number |-| `touchSoundDisabled` (Android) | If set to true, prevents the system sound from playing on touch. | Boolean |+|`accessibilityIgnoresInvertColors` (iOS)|Indicates whether the view should be inverted when color inversion is enabled. A value of `true` prevents inversion even if color inversion is turned on. See the Accessibility guide for more information.|Boolean|+|`accessible`|When set to `true`, marks the view as an accessibility element. By default, all touchable elements are accessible.|bool|+|`accessibilityLabel`|Overrides the text read by screen readers when interacting with the element. By default, it is constructed from all child `Text` nodes separated by spaces.|string|+|`accessibilityLanguage` (iOS)|Specifies the language used by the screen reader for this element, following the BCP 47 specification. See the iOS `accessibilityLanguage` documentation for more information.|string|+|`accessibilityHint`|Provides a hint to help users understand what will happen when they perform an action on the accessibility element if it's not clear from the label.|string|+|`accessibilityRole`|Communicates the purpose of a component to assistive technology users. Possible values include `'none'`, `'button'`, `'link'`, `'search'`, `'image'`, `'keyboardkey'`, `'text'`, `'adjustable'`, and more.|string|+|`accessibilityState`|Describes the current state of a component to assistive technology users. See the Accessibility guide for more information.|object: `{disabled, selected, checked, busy, expanded}`|+|`accessibilityActions`|Allows assistive technologies to programmatically invoke actions on a component. Each action should include a name and label. See the Accessibility guide for more details.|array|+|`aria-busy`|Indicates that an element is being modified and assistive technologies may want to wait until changes are complete before notifying the user.|boolean|+|`aria-checked`|Represents the state of a checkable element, which can be either a boolean or `'mixed'`.|boolean, 'mixed'|+|`aria-disabled`|Indicates that an element is perceivable but disabled and not editable or operable.|boolean|+|`aria-expanded`|Shows whether an expandable element is currently expanded or collapsed.|boolean|+|`aria-hidden`|Specifies if the accessibility elements within this element are hidden, affecting how assistive technologies like VoiceOver interact with sibling views.|boolean|+|`aria-live` (Android)|Indicates updates to an element and describes the types of updates expected by user agents, assistive technologies, and users. Options include `'assertive'`, `'off'`, and `'polite'`.|enum: `'assertive'`, `'off'`, `'polite'`|+|`aria-modal` (iOS)|Boolean indicating whether VoiceOver should ignore sibling elements within views. Takes precedence over the `accessibilityViewIsModal` prop.|boolean|+|`onAccessibilityAction`|Invoked when an accessibility action is performed by the user. The function receives an event containing the name of the action to perform. See the Accessibility guide for more information.|function|+|`accessibilityValue`|Represents a component's current value, either as a textual description or range information (min, max, now) for components like sliders and progress bars.|object: `{min, max, now, text}`|+|`aria-valuemax`|Specifies the maximum value for range-based components, taking precedence over the `max` value in the `accessibilityValue` prop.|number|+|`aria-valuemin`|Specifies the minimum value for range-based components, taking precedence over the `min` value in the `accessibilityValue` prop.|number|+|`aria-valuenow`|Represents the current value for range-based components, taking precedence over the `now` value in the `accessibilityValue` prop.|number|+|`aria-valuetext`|Provides a textual description of the component's value, taking precedence over the `text` value in the `accessibilityValue` prop.|string|+|`delayLongPress`|Duration (in milliseconds) from `onPressIn` before `onLongPress` is called.|number|+|`delayPressIn`|Duration (in milliseconds) from the start of a touch until `onPressIn` is invoked.|number|+|`delayPressOut`|Duration (in milliseconds) after releasing a touch before `onPressOut` is called.|number|+|`hitSlop`|Defines how far from the button a touch can start. This value is added to `pressRetentionOffset` when moving off of the button. The touch area does not extend past parent view bounds and sibling views with higher Z-index take precedence if overlapping.|Rect or number|+|`id`|Used to locate this view from native code, taking precedence over the `nativeID` prop.|string|+|`onLayout`|Called on mount and during layout changes.|`({nativeEvent: LayoutEvent}) => void`|+|`onLongPress`|Triggered if the time after `onPressIn` exceeds 370 milliseconds, customizable with `delayLongPress`.|function|+|`onPress`|Called when a touch is released unless cancelled (e.g., by a scroll that steals the responder lock). The first argument is an event in form of PressEvent.|function|+|`onPressIn`|Invoked as soon as the touchable element is pressed, even before `onPress`. Useful for tasks like network requests. The first argument is an event in form of PressEvent.|function|+|`onPressOut`|Called immediately after a touch is released, prior to `onPress`. The first argument is an event in form of PressEvent.|function|+|`pressRetentionOffset`|Defines how far a touch may move off the button before deactivating it when the scroll view is disabled. Re-activation occurs upon moving back over the button. Pass a constant to reduce memory allocations.|Rect or number|+|`touchSoundDisabled` (Android)|If set to true, prevents the system sound from playing on touch.|Boolean|-The provided text appears to be a detailed documentation of various properties and methods associated with a `View` component, likely from a mobile development framework such as React Native. Below is an organized summary of these properties and their descriptions:···In the example above, the image size limit is set to 4 MB and the total cost limit to 200 MB.···-_In the browser_, if no size is given to an image, the browser renders a 0x0 element, downloads the image, and then displays it with the correct size. The issue here is that your UI will jump around as images load, leading to a poor user experience known as Cumulative Layout Shift.+*In the browser*, if no size is given to an image, the browser renders a 0x0 element, downloads the image, and then displays it with the correct size. The issue here is that your UI will jump around as images load, leading to a poor user experience known as Cumulative Layout Shift.-_In React Native_, this behavior isn't implemented intentionally. It requires more work for developers to know the dimensions (or aspect ratio) of remote images in advance, but it leads to a better user experience. Static images loaded from the app bundle via `require('./my-icon.png')` can be automatically sized because their dimensions are available immediately at mounting time.+*In React Native*, this behavior isn't implemented intentionally. It requires more work for developers to know the dimensions (or aspect ratio) of remote images in advance, but it leads to a better user experience. Static images loaded from the app bundle via `require('./my-icon.png')` can be automatically sized because their dimensions are available immediately at mounting time.······A unique identifier used to associate this `InputAccessoryView` with specific TextInput(s).·········- **`center`:** Center the image along both dimensions. If larger than the view, scale it down uniformly to fit within the view.Specifies how an image should be resized when its frame dimensions do not match the raw image dimensions.···Sets the drop shadow color. This property functions only on Android API 28 and above. For similar effects on lower APIs, use the `elevation` property.···-`boxShadow` is only available on the New Architecture. Outset shadows are supported on Android 9+, and inset shadows on Android 10+. This prop adds a shadow effect to an element, allowing control over position, color, size, and blurriness of the shadow. It can be either outside or inside the border box depending on whether it is _inset_. This implementation follows web standards.+`boxShadow` is only available on the New Architecture. Outset shadows are supported on Android 9+, and inset shadows on Android 10+. This prop adds a shadow effect to an element, allowing control over position, color, size, and blurriness of the shadow. It can be either outside or inside the border box depending on whether it is *inset*. This implementation follows web standards.···The offset on the x-axis. This value can be either positive or negative, where a positive value indicates a rightward shift and a negative value indicates a leftward shift.The offset on the y-axis. Similar to `offsetX`, this value can be either positive or negative, with a positive value indicating an upward shift and a negative value indicating a downward shift.This represents the standard deviation used in the Gaussian blur algorithm. A larger value results in a blurrier shadow. Only non-negative values are valid, with the default being 0.···Identifies the node ID of the element that receives the PressEvent. It can be a number, or it may be `null` or `undefined`.···The amount of force used during a 3D Touch press, represented as a float value ranging from `0.0` to `1.0`.The node ID of the element receiving the `PressEvent`. It can be a number or `null`/`undefined`.······React Native includes numerous Core Components for various functionalities, from basic controls to activity indicators. These are documented in the API section. Key Core Components include:-| `<View>` | `<ViewGroup>` | `<UIView>` | A non-scrolling `<div>` | Acts as a container supporting layout with flexbox, style, touch handling, and accessibility controls. |-| `<Text>` | `<TextView>` | `<UITextView>` | `<p>` | Displays, styles, nests text strings, and handles touch events. |-| `<Image>` | `<ImageView>` | `<UIImageView>` | `<img>` | Used for displaying various types of images. |-| `<ScrollView>` | `<ScrollView>` | `<UIScrollView>` | `<div>` | A generic scrolling container that can hold multiple components and views. |-| `<TextInput>` | `<EditText>` | `<UITextField>` | `<input type="text">` | Enables user text input. |+|`<View>`|`<ViewGroup>`|`<UIView>`|A non-scrolling `<div>`|Acts as a container supporting layout with flexbox, style, touch handling, and accessibility controls.|+|`<Text>`|`<TextView>`|`<UITextView>`|`<p>`|Displays, styles, nests text strings, and handles touch events.|+|`<Image>`|`<ImageView>`|`<UIImageView>`|`<img>`|Used for displaying various types of images.|+|`<ScrollView>`|`<ScrollView>`|`<UIScrollView>`|`<div>`|A generic scrolling container that can hold multiple components and views.|In the following sections, you will learn how to combine these Core Components to understand React's workings better.···> The `<>` and `</>` are JSX fragments. Adjacent JSX elements must be wrapped in an enclosing tag, which fragments allow without adding unnecessary wrapping elements like `View`.Having covered React and React Native’s Core Components, let's explore handling `<TextInput>` further.···Async Storage is a community-maintained module for React Native that provides an asynchronous, unencrypted key-value store. Each app operates in its own sandbox environment, preventing cross-app data access.·········**Description:** When set to `true`, views outside of the viewport are detached from the native view hierarchy.······**Description:** Sets the delay in milliseconds between batch renders for `VirtualizedList`.······**Description:** Measured in units where 1 equals the viewport height. The default is 21 (10 viewports above, 10 below, and one in between).···-| titleRequired | string | The dialog's title. Passing `null` or an empty string will hide the title. |+|titleRequired|string|The dialog's title. Passing `null` or an empty string will hide the title.|···-| callbackOrButtons | function \| AlertButton\[] | If a function, it is invoked with the prompt's value `(text: string) => void` when 'OK' is tapped.\*\*\*If an array, buttons are configured based on its content. |-| keyboardType | string | Keyboard type for the first text field (if present). One of `TextInput` keyboard types. |+|callbackOrButtons|function \| AlertButton\[]|If a function, it is invoked with the prompt's value `(text: string) => void` when 'OK' is tapped.\*\*\*If an array, buttons are configured based on its content.|+|keyboardType|string|Keyboard type for the first text field (if present). One of `TextInput` keyboard types.|············-| cancelableAndroid | boolean | Determines if the alert can be dismissed by tapping outside of it. |-| userInterfaceStyleiOS | string | Interface style for the alert, set to `light` or `dark`, otherwise defaults to system style. |+|cancelableAndroid|boolean|Determines if the alert can be dismissed by tapping outside of it.|+|userInterfaceStyleiOS|string|Interface style for the alert, set to `light` or `dark`, otherwise defaults to system style.|······The **React Native Hooks** library offers a convenient `useBackHandler` hook that simplifies setting up event listeners.···- (instancetype)init { if (self = \[super init]) { \_localStorage = \[\[NSUserDefaults alloc] initWithSuiteName:RCTNativeLocalStorageKey]; } return self; }-- (std::shared_ptr<facebook::react::TurboModule>)getTurboModule:(const facebook::react::ObjCTurboModule::InitParams &)params { return std::make_shared<facebook::react::NativeLocalStorageSpecJSI>(params); }+- (std::shared\_ptr<facebook::react::TurboModule>)getTurboModule:(const facebook::react::ObjCTurboModule::InitParams &)params { return std::make\_shared<facebook::react::NativeLocalStorageSpecJSI>(params); }- (NSString \* \_Nullable)getItem:(NSString \*)key { return \[self.localStorage stringForKey:key]; }···The following table serves as a reference for supported types and their mappings across different platforms:-| Flow | TypeScript | Flow Nullable Support | TypeScript Nullable Support | Android (Java) | iOS (ObjC) |-| Object Literal `{ foo: string, ...}` | `{ foo: string, ...} as const` | `?{ foo: string, ...}` | `?{ foo: string, ...} as const` | - | - |-| Object \[1] | Object \[1] | `?Object` | `Object \| null` | `ReadableMap` | `@` (untyped dictionary) |-| `Array<T>` | `Array<T>` | `?Array<T>` | `Array<T> \| null` | `ReadableArray` | `NSArray` (or `RCTConvertVecToArray` when used inside objects) |-| `Promise<T>` | `Promise<T>` | `?Promise<T>` | `Promise<T> \| null` | `com.facebook.react.bridge.Promise` | `RCTPromiseResolve` and `RCTPromiseRejectBlock` |-| Type Unions `'SUCCESS'\|'FAIL'` | Type Unions `'SUCCESS'\|'FAIL'` | Only as callbacks | | - | - |-| Callbacks `() =>` | Callbacks `() =>` | Yes | | `com.facebook.react.bridge.Callback` | `RCTResponseSenderBlock` |+|Flow|TypeScript|Flow Nullable Support|TypeScript Nullable Support|Android (Java)|iOS (ObjC)|+|Object Literal `{ foo: string, ...}`|`{ foo: string, ...} as const`|`?{ foo: string, ...}`|`?{ foo: string, ...} as const`|-|-|+|`Array<T>`|`Array<T>`|`?Array<T>`|`Array<T> \| null`|`ReadableArray`|`NSArray` (or `RCTConvertVecToArray` when used inside objects)|+|`Promise<T>`|`Promise<T>`|`?Promise<T>`|`Promise<T> \| null`|`com.facebook.react.bridge.Promise`|`RCTPromiseResolve` and `RCTPromiseRejectBlock`|+|Callbacks `() =>`|Callbacks `() =>`|Yes||`com.facebook.react.bridge.Callback`|`RCTResponseSenderBlock`|···-1. Follow the interactive menu until you reach the question: _"What type of library do you want to develop?"_+1. Follow the interactive menu until you reach the question: *"What type of library do you want to develop?"*-1. Select _Turbo module_ for this guide. You can create libraries for both New and Legacy Architectures.+1. Select *Turbo module* for this guide. You can create libraries for both New and Legacy Architectures.1. Choose whether your library will access platform-specific code (Kotlin & Objective-C) or use a shared C++ library.···This means, are you using the library on the native side or only in JavaScript? If it's just JavaScript, no further action is needed.······An enumeration of animation types used in the `create` method or within the `create`/`update`/`delete` configurations for `configureNext`.An enumeration of layout properties that can be animated, used in the `create` method or within the `create`/`update`/`delete` configurations for `configureNext`.-| spring | `{ duration: 700, create: { type: 'linear', property: 'opacity' }, update: { type: 'spring', springDamping: 0.4 }, delete: { type: 'linear', property: 'opacity' } }` |+|spring|`{ duration: 700, create: { type: 'linear', property: 'opacity' }, update: { type: 'spring', springDamping: 0.4 }, delete: { type: 'linear', property: 'opacity' } }`|·········-| **taskKey** | `string` | Required, the native ID for this task instance used when startHeadlessTask was called. |-| **taskProvider** | `TaskProvider` | Required, a promise-returning function that takes data from the native side as an argument. When resolved or rejected, the native side is notified and may destroy the JS context. |-| **taskCancelProvider** | `TaskCancelProvider` | Required, a void-returning function with no arguments; when cancellation is requested, the taskProvider should wrap up and return ASAP. |+|**taskKey**|`string`|Required, the native ID for this task instance used when startHeadlessTask was called.|+|**taskProvider**|`TaskProvider`|Required, a promise-returning function that takes data from the native side as an argument. When resolved or rejected, the native side is notified and may destroy the JS context.|+|**taskCancelProvider**|`TaskCancelProvider`|Required, a void-returning function with no arguments; when cancellation is requested, the taskProvider should wrap up and return ASAP.|······-| **taskKey** | `string` | Required, the native ID for this task instance used when startHeadlessTask was called. |-| **taskProvider** | `TaskProvider` | Required, a promise-returning function that takes data from the native side as an argument. When resolved or rejected, the native side is notified and may destroy the JS context. |+|**taskKey**|`string`|Required, the native ID for this task instance used when startHeadlessTask was called.|+|**taskProvider**|`TaskProvider`|Required, a promise-returning function that takes data from the native side as an argument. When resolved or rejected, the native side is notified and may destroy the JS context.|···············-| **taskId** | `number` | Required, the native ID for this task instance to track its execution. |+|**taskId**|`number`|Required, the native ID for this task instance to track its execution.|············Default renderer for every item in every section. Can be overridden per-section. Should return a React element.···A marker property for re-rendering since it implements `PureComponent`. Use this if your `renderItem`, Header, Footer, etc., depend on anything outside the `data` prop. Treat it immutably.Number of items to render initially. Should fill the screen but not much more. These items won't be unmounted for improved scroll-to-top performance.Rendered between each item, excluding top and bottom. By default, provides `highlighted`, `section`, and `[leading/trailing][Item/Section]` props. `renderItem` offers `separators.highlight`/`unhighlight` to update the `highlighted` prop, with custom props via `separators.updateProps`. Can be a React Component or element.Extracts a unique key for an item at a specified index. Used for caching and tracking item re-ordering. Defaults to checking `item.key`, then `item.id`, and falls back to the index.Adds "Pull to Refresh" functionality if provided. Ensure the `refreshing` prop is set correctly. Use `progressViewOffset={100}` to offset from the top.> Note: May have bugs (missing content) in some circumstances - use at your own risk. This may improve scroll performance for large lists.Rendered at the top of each section. Sticks to the top by default on iOS unless `stickySectionHeadersEnabled` is set otherwise.Rendered at the top and bottom of each section, different from `ItemSeparatorComponent`. Receives `highlighted`, `[leading/trailing][Item/Section]`, and custom props via `separators.updateProps`.Makes section headers stick to the top of the screen until pushed off by the next one. Enabled by default on iOS.······-| dataRequired | array | Data for rendering items in this section. Array of objects, similar to `FlatList`'s data prop. |-| key | string | Optional key for tracking section re-ordering. Defaults to array index if not specified. |-| renderItem | function | Optionally define an arbitrary item renderer for this section, overriding the default `renderItem`. |-| ItemSeparatorComponent | component, element | Optionally define an arbitrary item separator for this section, overriding the default `ItemSeparatorComponent`. |-| keyExtractor | function | Optionally define a custom key extractor for this section, overriding the default `keyExtractor`. |+|dataRequired|array|Data for rendering items in this section. Array of objects, similar to `FlatList`'s data prop.|+|key|string|Optional key for tracking section re-ordering. Defaults to array index if not specified.|+|renderItem|function|Optionally define an arbitrary item renderer for this section, overriding the default `renderItem`.|+|ItemSeparatorComponent|component, element|Optionally define an arbitrary item separator for this section, overriding the default `ItemSeparatorComponent`.|+|keyExtractor|function|Optionally define a custom key extractor for this section, overriding the default `keyExtractor`.|······Adds an event handler for various accessibility-related events. Supported events include:-| `accessibilityServiceChanged` (Android) | Fires when any accessibility services, such as TalkBack or third-party apps, are enabled. The argument is a boolean: `true` if enabled, otherwise `false`. |-| `announcementFinished` (iOS) | Fires after the screen reader finishes an announcement. Argument includes: - `announcement`: The announced string.<br>- `success`: Boolean indicating success of the announcement. |-| `boldTextChanged` (iOS) | Fires when bold text toggle state changes. Argument is a boolean: `true` if enabled, otherwise `false`. |-| `grayscaleChanged` (iOS) | Fires when grayscale toggle state changes. Argument is a boolean: `true` if enabled, otherwise `false`. |-| `invertColorsChanged` (iOS) | Fires when invert colors toggle state changes. Argument is a boolean: `true` if enabled, otherwise `false`. |-| `reduceMotionChanged` | Fires when reduce motion toggle state changes. Argument is a boolean: `true` if enabled or "Animation off" in Developer options, otherwise `false`. |-| `reduceTransparencyChanged` (iOS) | Fires when reduce transparency toggle state changes. Argument is a boolean: `true` if enabled, otherwise `false`. |-| `screenReaderChanged` | Fires when the screen reader's state changes. Argument is a boolean: `true` if enabled, otherwise `false`. |+|`accessibilityServiceChanged` (Android)|Fires when any accessibility services, such as TalkBack or third-party apps, are enabled. The argument is a boolean: `true` if enabled, otherwise `false`.|+|`announcementFinished` (iOS)|Fires after the screen reader finishes an announcement. Argument includes: - `announcement`: The announced string.<br>- `success`: Boolean indicating success of the announcement.|+|`boldTextChanged` (iOS)|Fires when bold text toggle state changes. Argument is a boolean: `true` if enabled, otherwise `false`.|+|`grayscaleChanged` (iOS)|Fires when grayscale toggle state changes. Argument is a boolean: `true` if enabled, otherwise `false`.|+|`invertColorsChanged` (iOS)|Fires when invert colors toggle state changes. Argument is a boolean: `true` if enabled, otherwise `false`.|+|`reduceMotionChanged`|Fires when reduce motion toggle state changes. Argument is a boolean: `true` if enabled or "Animation off" in Developer options, otherwise `false`.|+|`reduceTransparencyChanged` (iOS)|Fires when reduce transparency toggle state changes. Argument is a boolean: `true` if enabled, otherwise `false`.|+|`screenReaderChanged`|Fires when the screen reader's state changes. Argument is a boolean: `true` if enabled, otherwise `false`.|···-| options | object | Contains `queue`: If set to `true`, queues the announcement behind existing speech on iOS. |+|options|object|Contains `queue`: If set to `true`, queues the announcement behind existing speech on iOS.|···-| originalTimeout | number | The fallback timeout in milliseconds if no accessibility timeout is set. |+|originalTimeout|number|The fallback timeout in milliseconds if no accessibility timeout is set.|······-| reactNativeVersion | object | No | Information about React Native version. Keys are `major`, `minor`, `patch` with optional `prerelease` and values are `number`s. |-| BrandAndroid | string | No | The consumer-visible brand associated with the product/hardware. |-| uiModeAndroid | string | No | Possible values: `'car'`, `'desk'`, `'normal'`,`'tv'`, `'watch'` and `'unknown'`. Read more about Android ModeType. |-| forceTouchAvailableiOS | boolean | No | Indicates the availability of 3D Touch on a device. |-| interfaceIdiomiOS | string | No | The interface type for the device. Read more about UIUserInterfaceIdiom. |+|reactNativeVersion|object|No|Information about React Native version. Keys are `major`, `minor`, `patch` with optional `prerelease` and values are `number`s.|+|uiModeAndroid|string|No|Possible values: `'car'`, `'desk'`, `'normal'`,`'tv'`, `'watch'` and `'unknown'`. Read more about Android ModeType.|+|interfaceIdiomiOS|string|No|The interface type for the device. Read more about UIUserInterfaceIdiom.|·········Returns a boolean indicating if the device is an Apple Vision. Note that for Apple Vision Pro (Designed for iPad), `isVision` will be `false`, but `isPad` will be `true`.···Returns a boolean indicating if the application is running in Developer Mode with the testing flag set.·········The `select` method returns the most appropriate value based on the current platform. If running on a phone, keys for `android` and `ios` take precedence. If these are not specified, the `native` key is used, followed by the `default` key.·········-| contentRequired | object | - `message`: A message to share<br>- `url`: A URL to share<br>- iOS: `title`: Title of the message<br>- Android: At least one of `url` or `message` is required. |-| options | object | - Android: `dialogTitle`<br>- iOS: `excludedActivityTypes`, `subject` (a subject for email), `tintColor`, `anchor` (node to anchor the action sheet, used on iPad) |+|contentRequired|object|- `message`: A message to share<br>- `url`: A URL to share<br>- iOS: `title`: Title of the message<br>- Android: At least one of `url` or `message` is required.|+|options|object|- Android: `dialogTitle`<br>- iOS: `excludedActivityTypes`, `subject` (a subject for email), `tintColor`, `anchor` (node to anchor the action sheet, used on iPad)|·········- `change`: Triggers when a property within the `Dimensions` object changes. The argument to the event handler is of type `DimensionsValue`.···-| dimRequired | string | The name of the dimension as defined when calling `set`. Returns value for the dimension. |+|dimRequired|string|The name of the dimension as defined when calling `set`. Returns value for the dimension.|> Note: On Android, the `window` dimension excludes the size used by the status bar (if not translucent) and bottom navigation bar.············-- **callback**: _function_ (Required) - A function receiving an object with a `value` key set to the new value.+- **callback**: *function* (Required) - A function receiving an object with a `value` key set to the new value.······-- **callback**: _function_ (Optional) - A function receiving the final value after stopping the animation.+- **callback**: *function* (Optional) - A function receiving the final value after stopping the animation.···-- **callback**: _function_ (Optional) - A function receiving the original value after resetting the animation.+- **callback**: *function* (Optional) - A function receiving the original value after resetting the animation.·········On iOS devices, vibration functionality is achieved using the `AudioServicesPlaySystemSound(kSystemSoundID_Vibrate)` method.···This method stops any ongoing vibrations that were initiated with a repeating pattern by calling `vibrate()`.···-| pattern | number \| number\[] | `400` | Specifies either a single duration for vibration in milliseconds or an array of times. |-| repeat | boolean | `false` | If true, the vibration pattern will continue until `cancel()` is called. |+|pattern|number \| number\[]|`400`|Specifies either a single duration for vibration in milliseconds or an array of times.|+|repeat|boolean|`false`|If true, the vibration pattern will continue until `cancel()` is called.|······This property indicates the current font size scale. Some operating systems allow users to adjust their font sizes for better readability. This value reflects any such adjustments.··················
+25
-2
src/prettier.ts
+25
-2
src/prettier.ts
···