Receive UnexpectedArgsError when wrapping args/flags

[prescience-data]

Describe the bug
Not really a "bug" but more a DX issue, but thought I'd log it here in case there is interest in a PR.

In local dev testing we have a bash script that handles calling the oclif application from the top level of a monorepo (to avoid navigating down each time it's required).

# ./run
# Calls "<monorepo-root>/cli/bin/dev"
cd cli && rushx cli "${args}"

For shellcheck SC2086 the args are wrapped in double quotes.

Unfortunately, this triggers an UnexpectedArgsError when zero or > 1 args or flags are provided as the Parser sees them all as a single block.

To Reproduce
Steps to reproduce the behaviour:

1. Create an oclif start application called "cli"
2. Add a command with flags --foo and --bar that also callsthis.parse().
3. In the parent folder, create the bash script from above called ./run.
4. Execute ./run --foo
5. Command works ✅
6. Execute ./run (no args) or ./run --foo --bar=baz (multiple args)
7. Command throws UnexpectedArgsError on "" ❌

Expected behaviour
Would be amazing if the parser step here (or it's parent) could unwrap any double quotes from around args before parsing.

Environment:

• OS & version: Ubuntu 22.04 LTS
• Shell/terminal: bash

[mdonnalley]

@prescience-data I believe this is out of scope for oclif as it seems unique to the script you're using to execute the cli. I'm going to close this for now but please feel free to re-open if you think there's something that I'm missing here. Thanks!