fix(core): use URL encoding for path parameters - #109
Merged
Conversation
Coverage Report
|
mfabisiak
marked this pull request as ready for review
July 24, 2026 12:56
MattK97
approved these changes
Jul 24, 2026
MattK97
left a comment
MattK97
left a comment
Collaborator
There was a problem hiding this comment.
LGTM, one thing: encodeParam now only works for primitives (jsonPrimitive throws on arrays/objects)- fine as-is, i'd just add a note in the code.
…rt Enum types and improve URL encoding
…arameters and improve overload handling for encodeParam and encodePathParam
Member
Author
Now |
… and improve body processing
…prove error body deserialization
fix(core): decoding string responses
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.