Development to Production - #128
Merged
Merged
Conversation
… policy Sentry error context no longer includes the API server's domain/host in request URLs, and the privacy policy is updated to reflect Sentry usage.
Email already identifies the reporter; app_user_id was unnecessary personal data collection in the Contact Support flow.
Sentry recorded the absolute request URL in every network breadcrumb, which exposed the address of the user's self-hosted server. A beforeBreadcrumb hook now keeps only the path and query. The stripOrigin helper moved to shared/utils/strings and is reused by capture-api-error.
PRD-2809: Remove Amplitude analytics and apiUrl from Sentry error context
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
1 participant
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.
No description provided.