Add user email and name to feedback #93512
Merged
Conversation
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
github-actions
bot
added
the
Scope: Frontend
billyvg
pushed a commit
that referenced
this pull request
Jun 18, 2025
The `captureFeedback` call in
`static/app/views/settings/project/tempest/PlayStationSdkAccessModal.tsx`
was significantly refactored to align with Sentry's recommended API for
user context and to customize the feedback message.
Changes include:
* **User Context**: User details (`id`, `email`, `username`, `name`) are
now passed via `hint.captureContext.user` in the `captureFeedback`
options. This replaces the previous approach of setting the user email
via the `'user.email'` tag.
* **Message Body**: The `message` property now constructs a multi-line
string containing:
* `User: [Name]`
* `Email: [Email]`
* `Engines: [Engine1, Engine2]` (formatted with human-readable labels)
* `Org Slug: [Org Slug]`
* **Game Engines**: Game engines are now included directly in the
message body, formatted for readability, instead of being stored as a
separate tag.
* **Tag Cleanup**: Redundant tags such as `'user.email'`, `'org.slug'`,
and `gameEngines` were removed, retaining only `feature` and
`githubProfile`.
These modifications ensure user information is captured correctly
according to Sentry's API and provide a structured, human-readable
feedback message.
---------
Co-authored-by: Cursor Agent <[email protected]>
Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
andrewshie-sentry
pushed a commit
that referenced
this pull request
Jun 19, 2025
The `captureFeedback` call in
`static/app/views/settings/project/tempest/PlayStationSdkAccessModal.tsx`
was significantly refactored to align with Sentry's recommended API for
user context and to customize the feedback message.
Changes include:
* **User Context**: User details (`id`, `email`, `username`, `name`) are
now passed via `hint.captureContext.user` in the `captureFeedback`
options. This replaces the previous approach of setting the user email
via the `'user.email'` tag.
* **Message Body**: The `message` property now constructs a multi-line
string containing:
* `User: [Name]`
* `Email: [Email]`
* `Engines: [Engine1, Engine2]` (formatted with human-readable labels)
* `Org Slug: [Org Slug]`
* **Game Engines**: Game engines are now included directly in the
message body, formatted for readability, instead of being stored as a
separate tag.
* **Tag Cleanup**: Redundant tags such as `'user.email'`, `'org.slug'`,
and `gameEngines` were removed, retaining only `feature` and
`githubProfile`.
These modifications ensure user information is captured correctly
according to Sentry's API and provide a structured, human-readable
feedback message.
---------
Co-authored-by: Cursor Agent <[email protected]>
Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
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.
The
captureFeedbackcall instatic/app/views/settings/project/tempest/PlayStationSdkAccessModal.tsxwas significantly refactored to align with Sentry's recommended API for user context and to customize the feedback message.Changes include:
id,email,username,name) are now passed viahint.captureContext.userin thecaptureFeedbackoptions. This replaces the previous approach of setting the user email via the'user.email'tag.messageproperty now constructs a multi-line string containing:User: [Name]Email: [Email]Engines: [Engine1, Engine2](formatted with human-readable labels)Org Slug: [Org Slug]'user.email','org.slug', andgameEngineswere removed, retaining onlyfeatureandgithubProfile.These modifications ensure user information is captured correctly according to Sentry's API and provide a structured, human-readable feedback message.