Move `useNativeInit` inside options

Open
#5,814 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
react-native, typescript
Domain
mobile

Research direction

Start by tracing the Expo plugin configuration and the existing handling of useNativeInit. Update the configuration path so useNativeInit is read from options as shown in the proposed v9 example, and verify that the documented configuration matches the new shape.

Written by the indexing model from the issue text.

Description

Errors Feature React-Native

Move useNativeInit from a top-level Expo plugin prop into the options object in v9.

Currently:

["@sentry/react-native/expo", {
  "useNativeInit": true,
  "options": {
    "dsn": "https://key@sentry.io/123"
  }
}]

Proposed for v9:

["@sentry/react-native/expo", {
  "options": {
    "useNativeInit": true,
    "dsn": "https://key@sentry.io/123"
  }
}]

Context: https://github.com/getsentry/sentry-react-native/pull/5804#discussion_r2924366187

Dominant language
TypeScript
Stars
1.8k
Forks
367
Avg merge
1d 6h
Merged PRs (30d)
94

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-react-native

All issues in getsentry/sentry-react-native

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.