flaggy icon indicating copy to clipboard operation
flaggy copied to clipboard

Idiomatic Go input parsing with subcommands, positional values, and flags at any position. No required project or package layout and no external dependencies.

Results 19 flaggy issues
Sort by recently updated
recently updated
newest added

Would you consider adding an option to convert positional arguments to different types like flags do today?

Currently, slice flags are required to be specified multiple times. It could be helpful though to automatically parse commas in slice flag inputs into different values. Then again, it could...

proposal

I'm trying to migrate https://github.com/rfjakob/gocryptfs from stdlib to flaggy. It's nice so far, having slice types is great, binding positional arguments is great, but is there a way to align...

enhancement

How do I explicitly print out a subcommand's help text (usage)?

enhancement

I asked about this on the slack channel a while back. Since it is one of only two issues I have with flaggy, I thought I'd ask about it here....

enhancement

I have reviewed the documentation and I don't see a way to sort the out put of the flags when -h(elp) is used. Is this possible and if not, is...

enhancement

It could be convenient to pass in a pointer to a struct for options. Flaggy could loop over the struct fields, and depending on the property type and name, assign...

proposal

Modifying the sliceFlag example to include a subcommand like: ``` package main import "github.com/integrii/flaggy" func main() { // Declare variables and their defaults var stringSliceFlag []string var boolSliceFlag []bool //...

If following option is enabled: flaggy.DefaultParser.ProcessMultipleShorts = true following multiple options : -e -x -a -m -p -l can be written as: -exampl Since, it breaks previous behaviour, it is...

In some circles, using a single `-` means that the next character will be a single-character flag and if there are multiple letters, they should be treated like a list...

proposal