fix(cli): use UTF-8 encoding for vswhere.exe output#8865
Merged
amrbashir merged 1 commit intoFeb 15, 2024
Conversation
amrbashir
approved these changes
Feb 15, 2024
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
2 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.
descriptionproperty in thevswhere.exeoutput may contain non-UTF-8 encoding characters if the system language is set to CJK.serde_jsonfails to parse the output due to the inability to escape those non-UTF-8 characters.vswhere.exeprovides an option to output with UTF-8 encoding and is recommended when outputting JSON.