fix: Fix encoding for example scripts on Windows #613
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
Member
|
@copilot Why this change needed? Will it break the script usage in any other platform like MacOS / Linux? |
Contributor
|
@congminh1254 I've opened a new pull request, #614, to work on those changes. Once the pull request is ready, I'll request review from you. |
Pull Request Test Coverage Report for Build 20574836248Details
💛 - Coveralls |
There was a problem hiding this comment.
Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Member
|
Copilot saying that it's good to go 🥇 |
congminh1254
approved these changes
Dec 29, 2025
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.
This PR configures PowerShell to use
UTF-8output encoding to resolve character rendering issues on Windows.While PowerShell 7 already defaults to
Unicode (UTF-8), legacy version5.1uses theOEM United Statescode page, which frequently misinterprets non-ASCII data from the Box CLI.This fix ensures that international characters display correctly in older environments while maintaining a consistent experience across all platforms.