Debug assert to catch AsyncParseableCommand hierarchy issues

[rauhul]

It would be nice to add a code path in debug mode that asserts if a user has accidentally included an AsyncParseableCommand nested under a Sync one, as the async run entry point will not be called in this case.

[KeithBird]

It would be nice to add a code path in debug mode that asserts if a user has accidentally included an AsyncParseableCommand nested under a Sync one, as the async run entry point will not be called in this case.

typo: AsyncParseableCommand -> AsyncParsableCommand 😊

[KeithBird]

Does the following code correctly express this issue?

struct Math: ParsableCommand {
  static var configuration = CommandConfiguration(
    subcommands: [Add.self]
  )

  struct Add: AsyncParsableCommand {
    @Argument() var values: [Int] = []
  }
}

// Error: `Add` subcommand can't run asynchronously in `Math`

[MarcoEidinger]

@rauhul is the issue fixed with #436 ? Then issue can be closed

[rauhul]

Yes, good catch, verified locally.