Comments (4)
Seems reasonable but out of interest why would you put a struct tag with an empty string for the placeholder in the first place?
from go-arg.
Better example why I want to hide the placeholders:
Before:
Usage: arg [--config CONFIG] [--output OUTPUT] [--key KEY] [--quiet]
Options:
--config CONFIG, -c CONFIG
help me
--output OUTPUT, -o OUTPUT
help me
--key KEY, -k KEY help me
--quiet, -q help me
--help, -h display this help and exit
After:
Usage: arg [--config ] [--output ] [--key ] [--quiet]
Options:
--config , -c help me
--output , -o help me
--key , -k help me
--quiet, -q help me
--help, -h display this help and exit
The placeholder just destroys the readability of the help section (in my opinion at least), and this was only a small example.
from go-arg.
I could live with them if the options ended up like this though:
Usage: arg [--config CONFIG] [--output OUTPUT] [--key KEY] [--quiet]
Options:
--config, -c CONFIG help me
--output, -o OUTPUT help me
--key, -k KEY help me
--quiet, -q help me
--help, -h display this help and exit
This seems to be the norm with long and short option variants, which go-arg doesn't follow.
from go-arg.
Ah very good point!
from go-arg.
Related Issues (20)
- Parsing of type rune does not work HOT 5
- Feature idea: configuration file alternative to CLI | env arg HOT 8
- No error when required arg in subcommand is not provided HOT 3
- Feature request: Alias for subcommands HOT 4
- Incorrect behavior of the built-in help message for the help option HOT 1
- How slice is supposed to work HOT 2
- subcommands must be pointers to structs but args is a pointer to interface HOT 2
- The os.Args input shouldn't avoid the argv[0] HOT 2
- Inconsistent/wrong list arg parsing HOT 2
- pointer-embedded fields are not supported HOT 3
- Inline structs are not supported HOT 4
- Any plans for a new release soon? HOT 1
- exit code should be 2 on flag parsing error
- flags are a flat namespace HOT 2
- Choices for arguments HOT 2
- Default values are not fed into custom parsers HOT 1
- Can I hide the default error message HOT 1
- Why --help and -h flags don't work while using arg.Parse(&args) HOT 1
- too many positional arguments HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from go-arg.