Autocomplete validation refactor

[David-Moreira]

          I was just taking a brief look at `Autocomplete` validation, correct me if I'm wrong @stsrki 

but from what I can tell, in Autocomplete you either have to set the Validator or AsyncValidator parameters with your validation.


https://blazorise.com/docs/extensions/autocomplete

I believe Data Annotations aren't currently supported by Autocomplete in that case. Again correct me If I'm wrong.

Also I'd argue that we should remove the internal Validator and Validator / AsyncValidator and just have the validation work as regular Blazorise Validation would work, by wrapping with the Validations / Validator outside the Autocomplete.

Originally posted by @David-Moreira in #4628 (comment)

[David-Moreira]

@stsrki Let's consider if this is a worthy refactor

[PatrickBig]

I just ran into a need for this as well. It would be a worthy addition

[WayneHiller]

Autocomplete having it's own Validation is causing me a lot of problems because I use Fluent Validation everywhere else in my app.

[spingee]

Its not possible to use dataannotation/fluent validations at all when heavily used autocomplete does not support it...

[stsrki]

Hello. We are aware of the limitations with validation on Autocomplete. But due to the needed changes we are planning to do it in 2.0 release.

[Hyppothalamus]

Are their any updates on this topic?

[stsrki]

It is planned for 2.0. We haven't started working on this feature yet because we had first to refactor input APIs, see #5732

Now that that is mostly done, we can start working on Autocomplete. But it is not going to be released soon.