Skip to content

optional arguments #31

@suntong

Description

@suntong

The GNU getopt supports optional arguments:

A long option normally begins with '--' followed by the long option
name. If the option has a required argument, it may be written
directly after the long option name, separated by '=', or as the next
argument (i.e. separated by whitespace on the command line). If the
option has an optional argument, it must be written directly after the
long option name, separated by '=', if present.

Would cli support optional arguments as well? If true, please make it clear of the following three stages:

  1. not specified
  2. specified but no argument
  3. specified and with argument

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions