Thoughts on CLI flags
See original GitHub issueCame across this comment from @jamestalmage:
My feeling on options via
cli.js
: We should only add those where users would conceivably want to temporarily override the contents of theirpackage.json
config. Allowing different reporters on CI servers, running in--serial
mode occasionally to debug, these are good examples.
I quite like this! Maybe it should be our “official” stance.
I think that’d mean --require
has to go. On the other hand the --source
flag may have to stay (as opposed to #937). We shouldn’t have --extension
either (#631).
Thoughts?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
CLI Flags Explained · oclif: The Open CLI Framework
The short flag form is quicker to type, and is often better for frequently used commands. Short flags are especially useful when stacking...
Read more >When to Use Long (Word) or Short (Letter ... - Nick Janetakis
Someone recently DM'd me and asked: Hi Nick, is there a difference or best practice between using word or letter options, example --all...
Read more >Command line arguments anatomy explained with examples
Analyze of the anatomy of command line (CLI) arguments with comparision of flags, named and positional arguments.
Read more >Is there a difference between a command line flag and a ...
"Flags" specifically, are Boolean arguments, set by the mere inclusion of the command-line argument, with no additional data needed or ...
Read more >When to Use Long (Word) or Short (Letter ... - YouTube
When to Use Long (Word) or Short (Letter) Command Line Flags ? 631 views 11 months ago.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That seems unlikely to be truly useful. Why would you want to avoid rerunning when certain sources change, but not others?
Great! I’ve updated the relevant issues and opened #1069 to remove the
--require
flag.