Open luispadron opened 4 months ago
I just encountered the same problem.
Also just hit this.. thought I might've been holding it wrong. I can try and take a look
Given the headaches and challenges around supporting the sync and async versions of run()
, I'm reticent to provide another overload here. As a workaround, you can perform any async validation at the start of your async run()
method – if you throw a ValidationError
from there you'll get the same output as an error thrown from the validate()
method.
If this workaround doesn't work for you, please let me know!
Yeah that works and it's what we do today but it lacks a few things:
Currently to share arguments across commands you can create a
ParsableArguments
type which contains your arguments/options, and can usefunc validate() throws
to validate the arguments.This fails for things that must be validated in an async manner. We should consider adding an async API for validating or
AsyncParsableArguments
to support this.