Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify the location of tracing's Context interaction. #1187

Merged
merged 4 commits into from
Nov 5, 2020
+2 −4
Merged

Clarify the location of tracing's Context interaction. #1187

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c5320a4
Clarify the location of tracing's Context interaction.
carlosalberto Nov 3, 2020
5faaacb
Update specification/trace/api.md
carlosalberto Nov 3, 2020
e14324e
Update specification/trace/api.md
Nov 4, 2020
a48f98d
Comma and restructure of text
Nov 4, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions specification/trace/api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,10 +149,9 @@ the following functionality:
- Set the currently active span to the implicit context. This is equivalent to getting the implicit context, then inserting the `Span` to the context.

All the above functionalities operate solely on the context API, and they MAY be
exposed as static methods on the trace module, as static methods on a class
inside the trace module (it MAY be named `TracingContextUtilities`), or on the
[`Tracer`](#tracer) class. This functionality SHOULD be fully implemented in the
API when possible.
exposed as either static methods on the trace module, as static methods on a class
bogdandrutu marked this conversation as resolved.
Show resolved Hide resolved
inside the trace module, or on the [`Tracer`](#tracer) class. This functionality
carlosalberto marked this conversation as resolved.
Show resolved Hide resolved
SHOULD be fully implemented in the API when possible.

## Tracer

Expand Down