Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Consider using the Global scope for static APIs (like setUser...)

Open
#4,915 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
react-native, typescript
Domain
mobile

Research direction

Start by reading the discussion linked from PR #4901 and trace the React Native static APIs, especially Sentry.SetUser, to determine their current scope behavior. Done means deciding and implementing whether these APIs should use the global scope for the single-user context while preserving the intended v7 behavior.

Written by the indexing model from the issue text.

Description

Errors Improvement React-Native
Description

On react native context, where we only have one user, Sentry.SetUser could use the global scope instead of an isolation scope.
We could target v7 with this change.

context: https://github.com/getsentry/sentry-react-native/pull/4901#discussion_r2142456956

Dominant language
TypeScript
Stars
1.8k
Forks
369
Avg merge
20h 55m
Merged PRs (30d)
105

Getting set up

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.