getsentry / getsentry/sentry-react-native
Make `useDispatchedActionData` default to `true` in the next major version
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 366
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 94
Description
The `ReactNavigationIntegration` has a `useDispatchedActionData` option (currently defaulting to `false`) that uses dispatched action data to improve navigation span quality:
* Names spans immediately from the action payload instead of starting with a generic "Route Change" name
* Skips spans for actions without a known route name (GO_BACK, POP, POP_TO_TOP, RESET), reducing noise
* Filters out non-navigation actions (SET_PARAMS, OPEN_DRAWER, CLOSE_DRAWER, TOGGLE_DRAWER)
This option was introduced as opt-in to avoid breaking changes, but it provides a strictly better experience for all users. In the next major version (9.x), we should flip the default to true.
Contributor guide
Research direction
Locate the ReactNavigationIntegration definition and the useDispatchedActionData option, then check how its default is declared for the upcoming 9.x major version. Change the default to true and verify that the documented action-name, skipped-span, and filtering behavior remains covered by the existing integration tests, if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100