- Code must be readable, therefore big functions and methods should not appear when we're increasing number of validation rules.
Clean code
- Domain layer must be isolated from other layers
Clean architecture
- Entity must never enter invalid state
Always-Valid domain model principle from DDD
- Application layer should have an opportunity to pass properly structured validation errors to presentation layer.
- All possible validation error should be easily displayable somewhere (for example, QA engineer might need all possible not 500-th errors which might appear on one every endpoint)
-
Notifications
You must be signed in to change notification settings - Fork 0
Example of validation which doesn't violate Domain-Driven Design principles.
License
TbotaPhantA/ddd-validation
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About
Example of validation which doesn't violate Domain-Driven Design principles.
Resources
License
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published