Nate Cook

Add methods for finding subsequences in a collection

4

### _Work in Progress_ --- ### Description Methods for finding the first, last, or all ranges of a given subsequence. ### Detailed Design TK ### Documentation Plan Guide and docs...

There should be API added to the `CommandConfiguration` type so that command authors can disable interactive mode. We'll need to choose a good name — something like `promptForMissingRequiredValues: Bool =...

[GSoC] Interactive mode should only run in an interactive shell

1

Tests are currently blocked on the `feature/interactive` branch because the interactive mode is always on. It should only run when the command is executed in an interactive shell.

[WIP] Add ArgumentSource as the projected value of arguments

2

### Description This adds a new `ArgumentSource` type as the projected value for `@Argument`, `@Option`, and `@Flag` types. This way, you can access the original string and location in the...

Group and label option groups in the help screen

1

Option groups are currently just splatted into the rest of the declared arguments for a command. This is sometimes fine, but often it would be nice if option groups were...

As pointed out in #120, there isn't any documentation describing how to manually create instances of `ParsableArguments` or `ParsableCommand` types, and the error message when using one created from calling...

Add a "Development" guide

3

The guide should cover pull request and testing expectations, coding style (re: [this note](https://github.com/apple/swift-argument-parser/pull/22#issuecomment-593087110)), and any platform-specific requirements.

Add two new `ArgumentArrayParsingStrategy` options

1

### Description This adds two new parsing options for argument arrays, and renames `.unconditionalRemaining` to `.captureForPassthrough`: - `unconditionalRemaining` has been an attractive nuisance. It looks like it means "everything leftover",...

Warn/validate commands with optional arguments before non-optional

1

As described in #489, a command that declares an optional `@Argument` before a non-optional `@Argument` won't ever allow a single-argument call. It would be nice if ArgumentParser provided a validation...

Once 1.2.0 is released, the code sample change in #498 should be reverted.