Asynchronous method validations #292
Comments
The original intent of Generally, the thinking is if you need to do a validation that requires an asynchronous call it would not be through this part of the framework. It is an interesting idea however to have something akin to this but I'm not sure it would be the current Thanks, |
@cacoco ok thanks I currently use |
@fayimora it doesn't mean you can't or shouldn't do it that way. It just means we didn't design the current implementation of Like I mentioned, it's an interesting idea but we probably wouldn't tie it to |
Currently,
@MethodValidation
requires the method to returnValidationResult
. Would it be possible to also support returningFuture[ValidationResult]
? Recently, I've had situations where my validation check returns aFuture
so I have to do something like:but that returns a
Future[ValidationResult]
The text was updated successfully, but these errors were encountered: