Change:
Issue Type: <bBug</bWhen I tried this in to create a new folder, and open it. Visual Code opens a newly created (unsaved) file named 301, what I expected to be is open the newly created folder as current workspace ! VS Code version: Code 1.31.1 (, 2019-02-12T02:21:36.727Z) OS version: WindowsNT ia32 6.1.7601 <details<summarySystem Info</summary </details<details<summaryExtensions (63)</summaryExtensionVersion ------ language-x86-64-assembly2.2.11 semantic-ui-snippets0.0.7 better-comments2.0.3 html-snippets0.2.1 vscode-javascript-snippet-pack0.1.5 vsc-prolog0.8.23 code-gnu-global0.2.2 vscode-django0.19.0 django-html1.3.0 django-snippets1.1.1 solargraph0.19.3 vscode-astyle0.9.0 scala0.0.5 jupyter1.1.5 scala-lsp0.2.3 vscode-ghc-simple0.0.10 vscode-npm-script0.3.5 vsc-material-theme2.7.0 lex-flex-yacc-bison0.0.3 vscode-npm3.3.0 reasonml1.0.38 vscode-atom-javascript-snippet0.2.1 ruby0.1.0 vue-snippets0.1.11 haskell-linter0.0.6 vscode-ghc-mod1.2.0 Ionide-fsharp3.34.0 Scala0.1.7 mysql-syntax1.3.1 language-haskell2.5.0 wordcounter1.4.0 vscode-sbt-scala0.2.4 MagicPython1.1.0 rainbow-csv1.0.0 cpplint0.1.3 mssql1.4.0 anaconda-extension-pack1.0.1 cpptools0.21.0 PowerShell1.11.0 wordcount0.1.0 vsliveshare0.3.1284 scala0.1.4 vetur0.16.2 vscode-code-outline0.1.1 open-html-in-browser1.0.4 word-counter0.0.1 tcl0.1.0 prolog0.0.4 ruby0.22.2 scheme0.0.2 java0.40.0 vscode-yaml0.3.0 tcl-outline0.2.1 tcl0.2.0 vscodeintellicode1.1.3 vscode-java-debug0.16.0 vscode-java-dependency0.3.0 vscode-java-pack0.6.0 vscode-java-test0.14.1 vscode-maven0.15.0 vsopen10.0.1 jinja0.0.8 plsql-language1.7.0 (5 theme extensions excluded) </details<!-- generated by issue reporter --
Looks like it only behaves like this when a folder has a leading 0. If someone wants to look into it, feel free.
I will look into this.
This has to do with the minimist argument parser detecting the unknown path argument as a number, and thus returning a number. As you noted, this case only really happens if the argument has a leading 0. The only solution I could think of to avoid this behavior would be to check if any input arguments start with a 0, and then append a character to the end so that it isn't detected as a number, and then remove the character after it has been parsed. I feel like this could work since I think the only arguments that could start with zero would be folder and file names, so it wouldn't be breaking anything else. I may be missing something though, and I understand if this isn't the way you want to fix this. I'll open the pull request with my fix for you to look at.
tells me we should define that should be a string. Something like the following, over : Wanna try that?
Yep, that worked. Thank you. I committed the new fix.

Discussion:
{ id: 'trace-category-filter', type: 'string' }, { id: 'trace-options', type: 'string' }, { id: 'prof-code-loading', type: 'boolean' }, <del> { id: 'nodeless', type: 'boolean' } // TODO@ben revisit electron5 nodeless support </del> <ins> { id: 'nodeless', type: 'boolean' }, // TODO@ben revisit electron5 nodeless support { id: '_', type: 'string' } </ins> ]; export function parseArgs(args: string[], isOptionSupported = (_: Option) => true): ParsedArgs {