Nate Cook

@mattt That looks like the right hierarchy to me, though tools should probably avoid allowing both config files and environment settings. Shaking my head thinking about the debugging nightmares for...

We don't have a workaround for this right now. For an option, you can specify the `.unconditional` parsing strategy, but arguments don't provide that capability. The changes in #29 will...

Still working on getting CI set up for this project — once that's in place we can look at adding steps to it. I'd love to have a linter take...

`try Notifier.parse()` will try to parse the command-line arguments to your program. Could you paste the rest of what's printed? I'd like to see what arguments it's seeing.

Thanks for this, @swiftyfinch — I'm not totally convinced that this is the right design to solve this issue, but it does seem sensible. Can you make sure the behavior...

@swiftyfinch I think only committers can kick off CI… Just let me know when you're ready for review!

@swift-ci Please test

@Zoha131 Thanks for your interest in working on this! > 1. Would the aliasing be an opt-in feature? Yes — I think the aliases could just be an array of...

The parsing always extracts labeled values (options and flags) first, and treats the remaining inputs as positional arguments, so I believe you'd be able to call something with two implicit/named...

Thanks for the bug report, @erica! Could you show the command declaration for this? I can’t quite get this error to reproduce.