-
Notifications
You must be signed in to change notification settings - Fork 821
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
fix(parseKeyPairsIntoRecord): allow equals in baggage value #3974 #3975
Conversation
Hi @krosenk729, thank you for your contribution. It looks like there are still some tests that are failing. Looking a bit into it, it looks like some tests that already existed are now outdated (double equal is given as an invalid example, when it is in fact valid). Feel free to adapt those 🙂 |
thank you so much for taking a look @pichlermarc ... I (hopefully) fixed that so the changes are good. I also see github saying the branch is out of sync with |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #3975 +/- ##
=======================================
Coverage 92.37% 92.37%
=======================================
Files 321 321
Lines 9264 9264
Branches 1968 1968
=======================================
Hits 8558 8558
Misses 706 706
|
proposed fix for parseKeyPairsIntoRecord issue 3974
Hi @krosenk729, please also add a changelog entry in cc @dyladan I know you've done some work on the baggage spec, would you mind also taking a look at this PR? 🙂 |
@pichlermarc thanks! updated! |
proposed fix for parseKeyPairsIntoRecord issue 3974
hey @pichlermarc anything else I need to do for this one? thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@krosenk729, no nothing to do anymore. thanks! 🙂
Let's get that into the next release. 🙂
proposed fix for parseKeyPairsIntoRecord issue 3974
Which problem is this PR solving?
Baggage header values can contain equals as part of their value. parseKeyPairsIntoRecord was treating every
=
as a delimeterFixes #3974
Short description of the changes
This will allow
parseKeyPairsIntoRecord('key=something==')
to return parsed header valuesType of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
parseKeyPairsIntoRecord('key1=something==')
parseKeyPairsIntoRecord('key1=something==,key2=somethingelse')
Checklist: