fix(native-server): use semicolon to join PowerShell statements#285
Open
vbp1 wants to merge 1 commit intohangwin:masterfrom
Open
fix(native-server): use semicolon to join PowerShell statements#285vbp1 wants to merge 1 commit intohangwin:masterfrom
vbp1 wants to merge 1 commit intohangwin:masterfrom
Conversation
Replace space with semicolon when joining multiline PowerShell script to prevent syntax errors in directory picker.
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
1 participant
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.
Summary
Problem
When multiline PowerShell commands are joined with spaces, PowerShell fails to parse them correctly, causing the directory picker to fail on Windows.
Solution
Use semicolon (
;) as a statement separator instead of space when joining the script lines.