chore(core): Mark Span.getSpanJSON
method as internal
#10197
Merged
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 small PR just clarifies the API status of the
Span.getSpanJSON
method. This method is purely purposed for internal usage and users should not rely on it but instead onspanToJSON
.Why should it stay on the
Span
class anyway?Span
class instances externally, which isn't clean or particularly safe either.I originally intended to deprecate this method but after discussing this, we decided to just clarify the internal purpose instead. The way we use this function right now is pretty safe, compared to the alternative mentioned above.
ref #10184