Skip to content

More consistent naming of Tracer.start_*() methods with other language implementations#1

Open
itsderek23 wants to merge 1 commit intopalazzem:palazzem/scope-managerfrom
itsderek23:itsderek23/scope-manager-tracer-start-naming
Open

More consistent naming of Tracer.start_*() methods with other language implementations#1
itsderek23 wants to merge 1 commit intopalazzem:palazzem/scope-managerfrom
itsderek23:itsderek23/scope-manager-tracer-start-naming

Conversation

@itsderek23
Copy link
Copy Markdown

  • Renames Tracer.start_manual() => Tracer.start_span() so it is more consistent with the Java and Go APIs. This is a clearer indication that a Span is returned.
  • Renames Tracer.start_active() => Tracer.start_active_scope() to reflect that a Scope is returned.

…ages

* Renames `Tracer.start_manual()` => `Tracer.start_span()` so it is more consistent with the Java and Go APIs. This is a clearer indication that a `Span` is returned.
* Renames `Tracer.start_active()` => `Tracer.start_active_scope()` to reflect that a `Scope` is returned.
@itsderek23
Copy link
Copy Markdown
Author

If this makes sense, I'll submit a PR on https://github.com/palazzem/basictracer-python/tree/palazzem/scope-manager-implementation and update the method names as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant