Search results

Usage generated by built-in help flag prepends names of <code>OptionGroup</code>s to command stack if all arguments are optional

bugSomething isn't workingSomething isn't working

good first issueGood for newcomersGood for newcomers

Status: Open.

#578 In apple/swift-argument-parser;

· YourMJK opened on Jul 13, 2023

<code>title</code> argument passed to nested <code>@OptionGroup</code> has no effect

bugSomething isn't workingSomething isn't working

Status: Open.

#558 In apple/swift-argument-parser;

· MaxDesiatov opened on Mar 1, 2023

AsyncParsableCommand exits before running <code>run() async</code>

bugSomething isn't workingSomething isn't working

Status: Open.

#538 In apple/swift-argument-parser;

· julianiaccopucci opened on Jan 6, 2023

Option not being parsed correctly

bugSomething isn't workingSomething isn't working

Status: Open.

#371 In apple/swift-argument-parser;

· philippzagar opened on Nov 8, 2021

USAGE command name should always reflect the actual binary name

bugSomething isn't workingSomething isn't working

Status: Open.

#295 In apple/swift-argument-parser;

· eaigner opened on Apr 3, 2021

ArgumentParser spuriously exits with a zero status on certain errors

bugSomething isn't workingSomething isn't working

Status: Open.

#269 In apple/swift-argument-parser;

· lorentey opened on Feb 9, 2021

Incorrect flag in error message

bugSomething isn't workingSomething isn't working

Status: Open.

#136 In apple/swift-argument-parser;

· erica opened on May 7, 2020