feat: Deprecate user segment field #10210
Merged
Conversation
This file contains 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
mydea
approved these changes
Jan 17, 2024
| @@ -19,6 +19,7 @@ export function getDynamicSamplingContextFromClient( | |||
| const options = client.getOptions(); | |||
|
|
|||
| const { publicKey: public_key } = client.getDsn() || {}; | |||
| // TODO(v8): Remove segment from User | |||
There was a problem hiding this comment.
Nice, that means we won't need the scope anymore for the dsc, right? Cc @Lms24 we can simplify this a bit in V8 then 🎉
There was a problem hiding this comment.
yup no scope for the DSC!
size-limit report 📦
|
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.
See getsentry/sentry#58767 (comment)
Segment is no longer supported by the product, so we can remove it in v8.