Print valid command/flags when passing in an invalid value

[cristiand391]

Print valid command/flags when passing in an invalid value

[justinwilaby]

Hey Oclif team! Is there any movement on this? We're running into this on the heroku-cli.

[mdonnalley]

@justinwilaby No movement on it. We had #870 opened to solve this but it raised a lot of design questions that we never answered. What do you have in mind?

[justinwilaby]

@mdonnalley - I believe it makes sense to follow exiting idioms. The github CLI approach is familiar to users and comprises a typical UX - I'd roll with that approach. We have observed users append irrelevant flags and args to commands where oclif seems to just eat them by default. It would be useful to either provide suggestions as described here or throw an error so the CLI author can choose how to act on it.

[mdonnalley]

We have observed users append irrelevant flags and args to commands where oclif seems to just eat them by default. It would be useful to either provide suggestions as described here or throw an error so the CLI author can choose how to act on it.

It should already throw an error if you're on v2 or greater

❯ sf version --foo
 ›   Error: Nonexistent flag: --foo
 ›   See more help with --help

The github CLI approach is familiar to users and comprises a typical UX - I'd roll with that approach

So only showing usage and flags?

❯ gh pr status --foo
unknown flag: --foo

Usage:  gh pr status [flags]

Flags:
  -c, --conflict-status   Display the merge conflict status of each pull request
  -q, --jq expression     Filter JSON output using a jq expression
      --json fields       Output JSON with the specified fields
  -t, --template string   Format JSON output using a Go template; see "gh help formatting"

[git2gus]

This issue has been linked to a new work item: W-15103729