ref: Rename SentryTrace to TracePropagationContext#1206
Draft
szokeasaurusrex wants to merge 1 commit into
Draft
Conversation
This is done in preparation for #1200, as we intend to store the org ID on `TracePropagationContext`. The rename supports this, as it makes it clear that data in `SentryTrace` does not only come from the `sentry-trace` header.
szokeasaurusrex
force-pushed
the
szokeasaurusrex/generalize-sentry-trace
branch
from
a437178 to
31f0cea
Compare
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.
This is done in preparation for #1200, as we intend to store the org ID on
TracePropagationContext.The rename supports this, as it makes it clear that data in
SentryTracedoes not only come from thesentry-traceheader.