-
Notifications
You must be signed in to change notification settings - Fork 75
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 #569 - Manually encode Uri query parameters #596
Conversation
d40bbaa
to
2ec3411
Compare
Tests are failing, partial fix is in #595 (review appreciated) but the tests for this that were added pass. |
2ec3411
to
5c61416
Compare
5c61416
to
aefdf2b
Compare
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.
Thanks @sloshy ! LGTM
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.
Thanks 👍
Codecov Report
@@ Coverage Diff @@
## master #596 +/- ##
==========================================
+ Coverage 90.18% 90.22% +0.04%
==========================================
Files 25 25
Lines 611 614 +3
Branches 1 4 +3
==========================================
+ Hits 551 554 +3
Misses 60 60
Continue to review full report at Codecov.
|
Fixes #569. The solution to the issue of query parameters being encoded incorrectly lies within a recently-added workaround in http4s,
Query.fromString
, which preserves the string you pass to it without trying to apply its own encoding rules.Please let me know if the tests could be improved or if there is more documentation required.