Skip to content

Conversation

@JensAyton
Copy link
Contributor

Updates behaviour of withSpan to match documentation.

I would consider also making the context form of withSpan (which is untested) call into the baggage variant.

Fixes #30

@swift-server-bot
Copy link

Can one of the admins verify this patch?

4 similar comments
@swift-server-bot
Copy link

Can one of the admins verify this patch?

@swift-server-bot
Copy link

Can one of the admins verify this patch?

@swift-server-bot
Copy link

Can one of the admins verify this patch?

@swift-server-bot
Copy link

Can one of the admins verify this patch?

Copy link
Collaborator

@slashmo slashmo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking this on, @JensAyton! 👍 LGTM, just some minor nitpicks to clean up the assertions.

@slashmo
Copy link
Collaborator

slashmo commented Dec 14, 2020

I would consider also making the context form of withSpan (which is untested) call into the baggage variant.
@JensAyton

Sounds good to me. Would you mind adding this as well?

@tomerd
Copy link
Member

tomerd commented Dec 14, 2020

@swift-server-bot add to whitelist

@ktoso
Copy link
Member

ktoso commented Dec 15, 2020

Let me merge this and let's do

I would consider also making the context form of withSpan (which is untested) call into the baggage variant.

in a follow up please @JensAyton ?

Thanks a lot!

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.

withSpan() doesn’t work as documented

5 participants