This library forces you to define the validations of the model for it to work. This is incorrect and the validations should actually be defined on the controller. The rationale around this is that for different screens, the same model may have different validation requirements. Defining them in the model forces all screens to use the same validation logic.
Can this be updated to use validations from the controller instead of the model?
This library forces you to define the validations of the model for it to work. This is incorrect and the validations should actually be defined on the controller. The rationale around this is that for different screens, the same model may have different validation requirements. Defining them in the model forces all screens to use the same validation logic.
Can this be updated to use validations from the controller instead of the model?