Open Dreamescaper opened 3 years ago
Some open questions.
Naming. All Web Blazor forms components have Input prefix. Does it make sense here, considering that \<input/> tag has no relation here? EditForm would be a known name for developers with Web Blazor experience, but does it make sense here, considering that no \<form> control will be rendered?
Implementing those components as wrappers around original controls (e.g. ValidatedEntry over Entry, SubmitButton over Button) would require to redefine and forward all properties. Does it make sense to use code generation? Or is there any other way? Something like Xamarin Behaviors could work here, but don't think there's any Blazor alternative to that. Or would it be possible simply to inherit original components?
I would love to be able to use same validations techniques as in Web Blazor, with DataAnnotationsValidator or third-party FluentValidator.
I'd expect it to be something like that:
Those controls should probably go to separate project, e.g.
Microsoft.MobileBlazorBindings.Forms
orMicrosoft.MobileBlazorBindings.Validation
.