Repository navigation
feat: add user resolver - #2396
Merged
Merged
Conversation
decision-model-lintersdk
decision-model-linter: 1 call on 1 file, 2,332 input tokens, $0.000098, model typesafe/jev-1.13-20260917 The |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit bddd838. Configure here.
1 of 6 tasks
2 tasks done
Litarnus
pushed a commit
to getsentry/sentry-docs
that referenced
this pull request
Nov 19, 2026
<!-- Keep the urgency section so automation can prioritize this PR. You may delete other sections you don't need. --> ## DESCRIBE YOUR PR Documents `Scope::setUserResolver()` from getsentry/sentry-php#2396 on the PHP and Symfony Users page. It isn't released yet, so the version note says "newer than 4.37.1"; swap in the exact version once it ships. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) <!-- junior-request-attribution:start --> via [automation `evt_37e02acfecbc9f3cec3ed56026fa8080`](https://junior-prod.sentry.dev/automations/evt_37e02acfecbc9f3cec3ed56026fa8080) · Run ID `dispatch_8043c195d63b94f694d705950b210c12`. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:agent-dispatch%3Adispatch_8043c195d63b94f694d705950b210c12 --> -- [View Session](https://junior-prod.sentry.dev/conversations/agent-dispatch%3Adispatch_8043c195d63b94f694d705950b210c12) [[Sentry]](https://sentry.sentry.io/explore/conversations/agent-dispatch%3Adispatch_8043c195d63b94f694d705950b210c12/?project=4510944073809921) <!-- junior-session-footer:end --> --------- Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
2 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Adds a user resolver callback which can provide user information lazily. When it's defined, it will call the resolver every time
getUseris called. Setting data explicitly throughsetUserwill take precedence and the resolver will only be used to fill the remaining fields.The reason for adding this is that symfony provides a lazy firewall by default and trying to obtain user data will start the session, even if nothing else would have started it. By setting the provider we can start getting user data once it's available and will not start the session by accident.