-
Notifications
You must be signed in to change notification settings - Fork 939
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Best place for input validation? #96
Comments
it depends what and where you want to validate, |
In my case, I usually just handle validation logic in the repo and if validation fails I call a |
I believe it should be a result type of a sealed class of a "Result class per UseCase" approach. But input validation should occur in ViewModel. |
Depend on requirement. We can set validation on View, ViewModel or Model part also. |
I guess no validation logic is provided in this sample. Where is the best place to write validation logic in clean architecture? in Views, ViewModels, Use Cases, Models or Data Entities? Or maybe each layer must have its own validators?
The text was updated successfully, but these errors were encountered: