hellflame/argparse

Issues

• Is there a way to stop arguments from being interpreted as flags?

  #22 opened a year ago by Mrfiregem
  5

• Parent arguments are not handled when a sub command is defined

  #21 opened 2 years ago by b3j0f
  5

• [Discussion] expand features of Inheritable

  #18 opened 2 years ago by myOmikron
  8

• Inheritable options causes panic

  #17 opened 2 years ago by myOmikron
  8

• Struct for Commands and Routing by them

  #16 opened 3 years ago by agustin-del-pino
  4

• is it possible to specify global arguments for parser and sub-parsers.

  #15 opened 3 years ago by steven-varga
  9

• Use parameter without tag

  #14 opened 3 years ago by cowboy3d
  3

• Check for required in subparser only if subparser was invoked

  #11 opened 3 years ago by myOmikron
  5

• [Proposal] Return matched parser

  #12 opened 3 years ago by myOmikron
  3

• Required options are not display in help / usage string correctly

  #9 opened 3 years ago by myOmikron
  1

• Love your work!

  #8 opened 3 years ago by ArjixWasTaken
  4

• parser.Parse `args` evaluation

  #7 opened 3 years ago
  2

• Parse function is supposed to return an error type, instead it exits with os.Exit() which doesn't execute defer

  #6 opened 3 years ago by dartie
  2

• No way to determine which subcommand was called

  #2 opened 4 years ago by lespea
  9

• Short flags should be combined

  #3 opened 4 years ago by lespea
  1

• Are multiple subcommands possible?

  #1 opened 4 years ago by lespea
  4