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
Uri: inconsistent query param names (url-encode) when .renderString
-ing
#7127
Comments
.renderString
-ing
I am new to OSS contributing, but I would like to work on this issue. |
@tothpeti welcome, thank you! feel free to ask any questions here or on Discord and I encourage you to put up a draft PR very very early (e.g. just start by adding some failing tests) so everyone can follow along your progress and help where we can :) |
Unfortunately, I haven't been able to make any noticable progression with the ticket since I picked it up. This is why I will unassign myself from it. |
Uri seems to behave differently depending on where it "comes" from. Here's an example:
The biggest thing here is that two equal (
==
) queries produce different results with.renderString
.Another thing I'd argue - the colon (
:
) should not be url-encoded in this case (at least my quick googling of it suggests so). There might be other character not covered byorg.http4s.internal.UriCoding#QueryNoEncode
that should also not be url-encoded.The text was updated successfully, but these errors were encountered: