CLI on Windows: --folder-uri option only works as the last argument and when the --wait option is not present · Microsoft/vscode#209072

(7 留言) (0 反應) (1 負責人)TypeScript (74,848 star) (10,221 fork)batch import

buggood first issueteam-low-hangingwindowsworkbench-cli

描述

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.87.2
OS Version: Windows 10 Pro 19044.2486 VM

Steps to Reproduce:

Case where --folder-uri is not the last option. Run code --folder-uri vscode-remote://ssh-remote+vscode@some-workspace --disable-extension ms-vscode-remote.remote-containers --new-window --wait. Command will return immediately without action or error.
Case where --folder-uri is the last option but --wait is present. Run code --disable-extension ms-vscode-remote.remote-containers --new-window --wait --folder-uri vscode-remote://ssh-remote+vscode@some-workspace. Command will return immediately without action or error.

There seems to be a behavior where the the code command silently errors when --folder-uri and the --wait options are used together. Also, there seems to be a bug where the the code command silently errors when the --folder-uri option is not the last option.

貢獻者指南

技術棧: typescriptnodejs
領域: cli
議題類型: bug
難度: 3
預計時間: 1-3 hours
活動狀態: blocked
清晰度: clear
前置要求: Understanding of CLI argument parsingWindows environment
新手友善度: 35
研究方向: The issue is in the CLI argument parser, likely in files under `src/vs/platform/environment/`. Investigate how ` folder uri` and ` wait` options are parsed. Look for conditions that cause ` folder uri` to be ignored when not last or when ` wait` is present. Check comments in the issue for any reproduction variations or maintainer suggestions.