[FIX] Ensure proper handling of multi-byte characters in streams #280
Conversation
This file contains 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
The stream encoding needs to be set in order to properly handle multi-byte utf8 characters that are split between different chunks. See: https://nodejs.org/api/stream.html#stream_readable_setencoding_encoding
RandomByte
approved these changes
Feb 10, 2020
RandomByte
requested changes
Feb 10, 2020
There was a problem hiding this comment.
We need the same Node 8 exemption as in SAP/ui5-builder#411
RandomByte
approved these changes
Feb 10, 2020
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.
The stream encoding needs to be set in order to properly handle
multi-byte utf8 characters that are split between different chunks.
See:
https://nodejs.org/api/stream.html#stream_readable_setencoding_encoding