Skip to content

"Unknown argument: input" when specifying --no-input #1860

@AbigailBuccaneer

Description

@AbigailBuccaneer

Is this a feature request or a bug?

A bug.

What is the current behavior?

Currently --no-input is treated as an invalid argument. Passing --no-input=true works, but is cumbersome and surprising to users of the CLI.

$ web-ext lint --no-input 
web-ext lint

Validate the extension source

Options:
  --version                 Show version number                        [boolean]
  --source-dir, -s          Web extension source directory.
      [string] [required] [default: "/home/abigail/code/firefox-ctrlnumber/src"]
  --artifacts-dir, -a       Directory where artifacts will be saved.
                                                   [string] [required] [default:
                  "/home/abigail/code/firefox-ctrlnumber/src/web-ext-artifacts"]
  --verbose, -v             Show verbose output                        [boolean]
  --ignore-files, -i        A list of glob patterns to define which files should
                            be ignored. (Example:
                            --ignore-files=path/to/first.js path/to/second.js
                            "**/*.log")                                  [array]
  --no-input                Disable all features that require standard input
                                                                       [boolean]
  --config, -c              Path to a CommonJS config file to set option
                            defaults                                    [string]
  --config-discovery        Discover config files in home directory and working
                            directory. Disable with --no-config-discovery.
                                                       [boolean] [default: true]
  --output, -o              The type of output to generate
                            [string] [choices: "json", "text"] [default: "text"]
  --metadata                Output only metadata as JSON
                                                      [boolean] [default: false]
  --warnings-as-errors, -w  Treat warnings as errors by exiting non-zero for
                            warnings                  [boolean] [default: false]
  --pretty                  Prettify JSON output      [boolean] [default: false]
  --self-hosted             Your extension will be self-hosted. This disables
                            messages related to hosting on addons.mozilla.org.
                                                      [boolean] [default: false]
  --boring                  Disables colorful shell output
                                                      [boolean] [default: false]
  -h, --help                Show help                                  [boolean]

Unknown argument: input
$

What is the expected or desired behavior?

--no-input should be treated equivalently to --no-input=true.

Version information (for bug reports)

$ node --version
v13.10.1
$ yarn --version
1.22.4
$ web-ext --version
4.1.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions