jawher/mow.cli

Issues

• BoolsOpt() for repeated flags (Boolean options)?

  #123 opened 3 years ago by curio77
  1

• Spec is not inferred correctly for multi-value argument

  #127 opened 2 years ago by oakad
  0

• StringsOpt can not start with dashes

  #108 opened 4 years ago by mpldr
  12

• Extension: Quick start template

  #122 opened 3 years ago by TomFreudenberg
  1

• Example of writing test

  #117 opened 4 years ago by b00f
  1

• Wrapping long spec strings

  #121 opened 3 years ago by curio77
  0

• Global StringArg + command: contextual help does not work

  #118 opened 3 years ago by 3coma3
  4

• Handle sharing of options and arguments between subcommands

  #87 opened 6 years ago by nim-nim
  2

• Extension: check docker containerized starter with mow.cli as default

  #116 opened 4 years ago by TomFreudenberg
  0

• Possible bug with option specs

  #114 opened 4 years ago by skyzyx
  2

• Expose a model of the command structure

  #104 opened 5 years ago by skyzyx
  6

• Implement out-of-the-box support for shell autocompletion (source code available!)

  #113 opened 4 years ago by skyzyx
  0

• Custom exiter

  #112 opened 4 years ago by usernametaken
  0

• All flags look like booleans in -h output

  #82 opened 6 years ago by masiulaniec
  3

• The default value of the empty default option is not printed correctly

  #98 opened 4 years ago by daemtri
  1

• Add support to make a command hidden in cli

  #99 opened 4 years ago by vaishali-ntnx
  0

• Display missing required params

  #102 opened 5 years ago by Etomyutikos
  0

• Cannot use exclusive choices with OPTIONS

  #95 opened 6 years ago by sungo
  0

• Associate option values with specific arguments

  #94 opened 6 years ago by nim-nim
  0

• Provide a way to mark options as un-ordered

  #93 opened 6 years ago by nim-nim
  1

• Inter-option ordering

  #92 opened 6 years ago by nim-nim
  3

• Please make a release that includes the go.mod file

  #88 opened 6 years ago by nim-nim
  3

• Float Options

  #77 opened 6 years ago by tcurdt
  2

• Provide possibility of passing pointer to value for options or argument

  #83 opened 6 years ago by silasdavis
  1

• Catch duplicated command line flags

  #80 opened 6 years ago by silasdavis
  1

• Provide more specific parsing error feedback

  #84 opened 6 years ago by silasdavis
  1

• Add global panic interceptor

  #79 opened 6 years ago by oakad
  3

• Undeclared arg panic when using dynamic arg names

  #78 opened 6 years ago by coriolinus
  6

• Support environment variable as a *Opt parameter

  #59 opened 7 years ago by nmaupu
  4

• Synchronize README.md and doc.go

  #71 opened 7 years ago by pkazmier
  3

• CLI parsing chokes when optional value contains `=` char

  #74 opened 7 years ago by coriolinus
  1

• Command Usage strings do not include external arguments

  #67 opened 7 years ago by coriolinus
  0

• The app panics while parsing args

  #66 opened 7 years ago by olebedev
  2

• Position-independent options

  #64 opened 7 years ago by schmich
  4

• Negative values for VarArg() Bug?

  #65 opened 7 years ago by Javyre
  2

• Expose the target command inside Before/After listeners

  #62 opened 7 years ago by jawher
  0

• Help semantics are a bit confusing...

  #52 opened 7 years ago by DarwinJS
  1

• Application Hang

  #57 opened 7 years ago by iamyashrs
  3

• CLI hangs when EnvVar is set

  #55 opened 7 years ago by jdonboch
  3

• Cannot use func literal (type func(*cli.Cli)) as type cli.CmdInitializer

  #47 opened 7 years ago by kunashu
  2

• Consider tagging versions

  #48 opened 7 years ago by silasdavis
  2

• -h and --help do not honour the -- operator

  #41 opened 7 years ago by jawher
  1

• feature: support long descriptions for subcommands

  #45 opened 8 years ago by drewfish
  5

• Required environment variable

  #33 opened 8 years ago by gwatts
  5

• customize usage / help display

  #44 opened 8 years ago by pbkdf3
  2

• Aliasing commands

  #37 opened 8 years ago by gotwarlost
  5

• unsuccessful parsing in case of nested command

  #39 opened 8 years ago by the-shank
  3

• Possible to detect whether a value was specified by the user or is just the default value?

  #35 opened 8 years ago by evantorrie
  3

• custom types via flag.Value

  #32 opened 8 years ago by tv42
  3

• Request: parse expected flags with flag.ContinueOnError

  #30 opened 9 years ago by mark-kubacki
  4