https://github.com/michaelbe812/sheriff-demo
https://github.com/michaelbe812/sheriff-demo
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/michaelbe812/sheriff-demo
- Owner: michaelbe812
- Created: 2024-03-19T13:40:45.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2024-03-19T14:01:01.000Z (about 1 year ago)
- Last Synced: 2025-04-06T07:35:18.040Z (about 2 months ago)
- Language: TypeScript
- Size: 332 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# SheriffDemo
Sample repository demonstrating the usage of [sheriff](https://github.com/softarc-consulting/sheriff).
This demo showcases how to define architecture-boundaries for a complex setup. Within an application we want to have following structure:
```
/ (e.g. customer)
/ (e.g. feat-customer-support)
/smart-components
/ui-components
/data-access
/types
/util
/shared (domain-shared folder)
/shell
/shared
```
With sheriff we enfore following rules:
* we can not import between applications
* we can not import between domains
* we can not import between features in the same domain
* we allow imports between features in the same domain from the domain-shared or shared folder
* shell can only import from smart-components in the same domain
* smart-components can import from util, types, data-access and ui-components in the same feature
* ui-components can import from util, types, ui-components in the same feature
* data-access can import from util, types and data-access in the same feature
* types can import from types in the same feature
* util can import from util and types in the same feature