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.

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

W3CPropagation allows not having baggage #72

Merged
merged 1 commit into from
Sep 23, 2022

Conversation

marcingrzejszczak
Copy link
Contributor

without this change you will always parse baggage fields
with this change you can create a W3Propagation instance that doesn't use any baggage

without this change you will always parse baggage fields
with this change you can create a W3Propagation instance that doesn't use any baggage
@marcingrzejszczak marcingrzejszczak added the enhancement New feature or request label Sep 23, 2022
@marcingrzejszczak marcingrzejszczak added this to the 1.0.0-RC1 milestone Sep 23, 2022
@marcingrzejszczak marcingrzejszczak merged commit 29feef8 into main Sep 23, 2022
@marcingrzejszczak marcingrzejszczak deleted the w3cBravePropagationAllowsNoBaggage branch September 23, 2022 11:53
@marcingrzejszczak marcingrzejszczak restored the w3cBravePropagationAllowsNoBaggage branch September 23, 2022 14:14
@marcingrzejszczak marcingrzejszczak deleted the w3cBravePropagationAllowsNoBaggage branch September 23, 2022 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant