feat(core): Deprecate Span.origin
in favor of sentry.origin
attribute
#10260
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 PR deprecates the
Span.origin
field on the class and the interface. It will be replaced in v8 by the semanticsentry.op
attribute .For now, I didn't yet deprecate
SpanContext.origin
but I think we could do it quite easily by just setting the origin inattributes
when starting spans. Happy to tackle in a follow-up PR if we want to do this.ref #10184