New
Introducing React Bench, see how different models perform on React code

react-doctor/rn-prefer-pressable-over-gesture-detector

Use Pressable for a simple tap only when its press lifecycle preserves the Gesture.Tap callbacks and configuration

Status
Active
Category
React Native
Assessment
Evidence-required risk
Required evidence
source code
Default configuration
Enabled
Default severity
warn
Show technical metadata
Scope
React Native
Active when
framework=react-native and capabilities=react-native
Requirements
react-native
Tags
react-native, test-noise
Priority
34 (P3)
Source
oxlint-plugin-react-doctor
Rule set
oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
On this page

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires on a JSXOpeningElement whose resolved name is GestureDetector AND is imported from "react-native-gesture-handler", whose gesture={...} expression (inline, or one level of identifier binding via the variable's initializer) resolves to a CallExpression chain rooted at Gesture.Tap(): the chain's factoryName must equal "Tap", it must contain none of simultaneousWithExternalGesture/requireExternalGestureToFail/blocksExternalGesture, and any .numberOfTaps(arg) (using the OUTERMOST/effective call) must be the static numeric literal 1.

Suppress when: do NOT flag the non-tap or composed gestures the rule already excludes: Gesture.Pan()/Pinch() (factoryName !== "Tap") or a composition like Gesture.Race(Gesture.Tap(), Gesture.Pan())/Gesture.Simultaneous(...) whose chain root is Race/Simultaneous rather than Tap; multi-tap, namely numberOfTaps(2) or a non-literal/dynamic count like numberOfTaps(config.taps) or numberOfTaps(double ? 2 : 1) that Pressable cannot model; a tap chained to simultaneousWithExternalGesture/requireExternalGestureToFail/blocksExternalGesture; a GestureDetector named identically but imported from a local module; or a gesture prop bound to an unresolvable identifier (e.g. a prop) with no initializer chain to follow.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

  • Confirmed failure: The required evidence establishes the violation.
  • Rejected: A documented exception or false-positive predicate applies.
  • Needs evidence: Named evidence can still be collected.
  • Unavailable: Required evidence cannot be collected in this run.
  • Waived with evidence: An authorized, scoped exception applies to an established failure.
  • Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

For a confirmed simple tap, map lifecycle rather than renaming callbacks: activation/down behavior may map to onPressIn, successful completion to onPress, and finalization/release to onPressOut. Preserve enabled state, cancellation and movement thresholds, hitSlop, pressRetentionOffset, accessibility, pointer behavior, and any begin/end/finalize side effects; keep GestureDetector when Pressable cannot express them. For animated feedback, use an existing version-supported animated-Pressable pattern. createCSSAnimatedComponent from react-native-reanimated/css is Reanimated 4 CSS functionality and may be suggested only after confirming Reanimated 4 and the New Architecture; do not add or upgrade Reanimated for this rule. See https://reactnative.dev/docs/pressable

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.

Show repository-wide prompt

Fix every confirmed react-doctor/rn-prefer-pressable-over-gesture-detector diagnostic in the current repository.

Required change:

  • For a confirmed simple tap, map lifecycle rather than renaming callbacks: activation/down behavior may map to onPressIn, successful completion to onPress, and finalization/release to onPressOut. Preserve enabled state, cancellation and movement thresholds, hitSlop, pressRetentionOffset, accessibility, pointer behavior, and any begin/end/finalize side effects; keep GestureDetector when Pressable cannot express them. For animated feedback, use an existing version-supported animated-Pressable pattern. createCSSAnimatedComponent from react-native-reanimated/css is Reanimated 4 CSS functionality and may be suggested only after confirming Reanimated 4 and the New Architecture; do not add or upgrade Reanimated for this rule. See https://reactnative.dev/docs/pressable.

Validation before editing:

Fires on a JSXOpeningElement whose resolved name is GestureDetector AND is imported from "react-native-gesture-handler", whose gesture={...} expression (inline, or one level of identifier binding via the variable's initializer) resolves to a CallExpression chain rooted at Gesture.Tap(): the chain's factoryName must equal "Tap", it must contain none of simultaneousWithExternalGesture/requireExternalGestureToFail/blocksExternalGesture, and any .numberOfTaps(arg) (using the OUTERMOST/effective call) must be the static numeric literal 1.

Suppress when: do NOT flag the non-tap or composed gestures the rule already excludes: Gesture.Pan()/Pinch() (factoryName !== "Tap") or a composition like Gesture.Race(Gesture.Tap(), Gesture.Pan())/Gesture.Simultaneous(...) whose chain root is Race/Simultaneous rather than Tap; multi-tap, namely numberOfTaps(2) or a non-literal/dynamic count like numberOfTaps(config.taps) or numberOfTaps(double ? 2 : 1) that Pressable cannot model; a tap chained to simultaneousWithExternalGesture/requireExternalGestureToFail/blocksExternalGesture; a GestureDetector named identically but imported from a local module; or a gesture prop bound to an unresolvable identifier (e.g. a prop) with no initializer chain to follow.

Constraints:

  • Make the smallest change that fixes the root cause.
  • Preserve behavior and interfaces unrelated to this diagnostic.
  • Reuse existing project components, utilities, and conventions.
  • Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations.
  • Before editing, inspect the manifest, lockfile, native app configuration, React Native and Expo versions, and New Architecture status.
  • Also inspect the Reanimated major, installed list-library majors, and every affected platform-specific file.
  • Do not add or upgrade a native dependency, change linking, or alter Pods/Gradle setup unless explicitly authorized.
  • Do not enable the New Architecture or change Expo/native configuration unless explicitly authorized.
  • Preserve navigation, gesture, keyboard, safe-area, accessibility, lifecycle, and platform semantics; do not treat them as file-local import substitutions.
  • Verify behavior in a release build on each affected device platform in scope. Name any unavailable platform instead of claiming it passed.
  • Adapt identifiers and framework details instead of copying blindly.
  • Do not disable the rule or suppress matching code.
  • Confirm this rule is enabled for the project: framework=react-native and capabilities=react-native.

Assessment:

  • Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
  • Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
  • A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

Verification:

  • Run focused tests for the changed behavior.
  • Run React Doctor and confirm this diagnostic no longer appears from changed code.
  • Run an unfiltered scan of the affected scope before claiming no cross-category regression.
  • Report the files changed and any checks you could not run.