Convert strings to UTF-8 #1624
Merged
Convert strings to UTF-8 #1624
Conversation
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
Addresses the following offense: ``` [Correctable] Performance/UnfreezeString: Use unary plus to get an unfrozen string literal. ``` Caused by: `'café!'.dup`
|
Hi, I seem to have a problem caused by this: Maybe the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
If the HTTP response body contains 8bit characters, and the adapter does not set the encoding of
bodyto UTF-8 (like here: lostisland/faraday-net_http#13), the logger middleware fails with an error such as this:With this PR, the body is converted to UTF-8, replacing any 8-bit characters with the replacement character (U+FFFD, �).