Feature Request
| Q |
A |
| New Feature |
yes |
| RFC |
no |
| BC Break |
no |
Summary
Current examples often group rules by feature (e.g., Controllers, Repositories). Instead, we should prioritize Clean Architecture (layers, dependency direction) in docs and examples to:
- Better reflect Arkitect's purpose
- Encourage sustainable design (domain protection, layer isolation)
- Scale better than feature-grouping
Suggested Changes:
- Showcase layering (e.g., Domain -> Application -> Infrastructure)
- Document enforcing dependency rules between layers
- Keep feature grouping as optional
Feature Request
Summary
Current examples often group rules by feature (e.g., Controllers, Repositories). Instead, we should prioritize Clean Architecture (layers, dependency direction) in docs and examples to:
Suggested Changes: