-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
Suggestion: rename CurrentSpan
/SetCurrentSpan
#185
Comments
Hey, @iredelmeier I would like to work on this. Could you help me what are exact changes required? |
@VineethReddy02 the change for this should basically be a find-and-replace for the function provided in current.go (which should probably also be renamed!) and their usages. With the caveat that a PR implementing this suggestion may get rejected on the basis of the suggestion itself getting rejected, this would definitely be a good first issue! Inconveniently, I'm unable to modify issue labels in this repo. Some more good first issues (definitely non-exhaustive!):
|
See also #299. |
@VineethReddy02 are you still able to work on this? |
Hey @iredelmeier so what |
@VineethReddy02 |
@rakyll proposed "WithSpan" as opposed to "ContextWithSpan". What do you think? I do feel that "Context" adds stutter here. If we went with "WithSpan", what's the opposite name? (I still like |
I like more |
Although the PR merged, I am open to renaming |
stale issue. |
* Upgrade to v0.10.0 version * Upgrade to v0.10.0 code changes * Update Changelog
Thoughts on renaming these to
SpanFromContext
andContextWithSpan
to be more idiomatic?The text was updated successfully, but these errors were encountered: