await Task.Delay(3000);to the ValidateAsync() - in fact I'm making an API call. This was supposed to have been fixed in 3.1 (I'm on .net5). After returning a failed validation and adding to the message store, the ValidationMessage is displaying the error ok, but I can still submit the form...any ideas. I haven't used your FluentValidator (trying to reduce payload since so far I only needed this once)
await Validate()and then pass the result to
void AddValidationResult(errors). So I think I'm doing that...why would ValidationMessage/ValidationSummary display the error and yet not prevent the submit?
Task Whateverand ignore the result
EventHandler<ValidationRequestedEventArgs> ValidationRequestedAsync => async (sender, args) => await ValidationRequested(sender, args);and
EventHandler<FieldChangedEventArgs> FieldChangedAsync => async (sender, args) => await FieldChanged(sender, args);and change the ValidationRequested and FieldChanged to return Task, I have the same issue.
MustAsync(async () => ..) using your library right?
awaitwill occur immediately before returning to the caller
HandleSubmitAsync()that the developer has included the comment
var isValid = _editContext.Validate(); // This will likely become ValidateAsync laterso I guess I'll wait. As always, thanks for your help Peter.
So, unfortunately I need to use this channel to discuss an issue. I upgraded to Net 5 and found the same problem as mrpmorris/blazor-validation#19
What is blocking this issue? The Net 5 sample?
Just a warning.
FluentValidation 10 was released yesterday. In the release notes states that a lot of internal changes happened.
So I tried BlazorValidation and yes, it's not working with version 10.
No rush to update to v10, so still haven't looked if I can find where the problem is.