Welcome to the .NET MAUI feedback portal. We’re happy you’re here! If you have feedback on how to improve the .NET MAUI, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

Hi,

I have noticed that utility of SfDataForm is somewhat diminished with the way it's validation was realized:

  1. It's hard to do custom validation.
  2. It's not aligned with MVVM architecture, where validation should be performed in viewmodel.

I would suggest to, instead of having the form perform validation, have it delegate validation to other parties (viewmodel for example), and then bind to observable object that contains errors for each property. Object to bind to could have the standard IDataErrorInfo contract, providing all the necessary events and data.

SfData form could provide following:

  1. Bindable property for observable error list where errors can be associated with property names
  2. View section for errors not associated with any property (or associated with multiple properties)
  3. A Command with property name parameter to bind validation logic for single property
  4. A Command without parameters to bind validation logic for the whole data object.

Soo, that's the general idea, I think it would make the component much easier to work with.