Adding a CancellationToken token parameter to ValueTask functions in the Validators.

[emorell96]

I think this could be useful specially for more complex custom validations where it might be efficient to be able to cancel the validation if needed.

Right now this is not possible specially in the case where you create something like MultiValidationBehavior using your own implementation. Since MultiValidationBehavior uses an internal method internally (ValidateNestedAsync) which is not available to the library users.

A workaround this is to use ForceValidate() which returns a ValueTask so it can be awaited like the one above, but the disadvantage of this one is that it doesn't take a CancellationToken meaning that it cannot cancel the validation once underway.

For simple validations it isn't a big deal, but for more complex longer running validations it is.

I think it would be nice to make sure that all awaitable methods in the validators can accept a CancellationToken if possible.

Specially ForceValidate since the underlaying method already accepts it.

What do you all think? I'd appreciate your input.

[VladislavAntonyuk]

It would be nice to add CancellationToken to all methods, which return Task

[brminnick]

Agreed! And, to be honest, I'm a little embarrassed that we didn't implement this from the beginning 🙂

[CliffAgius]

Closed as per the Community Stand-up discussion here: https://youtu.be/N9wMcBP4jtg?t=2889