11 Directory Structure conform Clean Architecture

[thomasdejaeghere]

Directory structure for backend and frontend is ready for implementation. The structure is conform clean architecture and files for all needed entities (as described by @brentjan) have been made. You can see a basic scheme of the structure below this message. I also added a few example use-cases, these can be used, deleted, modified at will. Now we can set-up the right issues to split up the work over the different entities and use-cases needed for the project.

backend/
│── src/
│ ├── core/ # (Entities & Use Cases)
│ │ ├── entities/ # Domain models (pure TypeScript classes)
│ │ ├── use-cases/ # Business logic use cases
│ ├── infrastructure/ # (External dependencies)
│ │ ├── database/ # TypeORM entities & database config
│ │ ├── repositories/ # Data access layer (TypeORM Repos)
│ ├── application/ # (Interface Adapters)
│ │ ├── controllers/ # Express route handlers
│ │ ├── services/ # Application services
│ │ ├── routes/ # Definitions of routes for entities
│ ├── config/ # Basic interfaces for frequently used classes
│ ├── index.ts

frontend/
│── src/
│ ├── app/
│ │ ├── core/ # (Business logic, use cases if needed)
│ │ ├── infrastructure/ # (External dependencies)
│ │ │ ├── api/ # API services
│ │ │ ├── guards/ # Route guards
│ │ ├── components/ # Reusable UI components
│ │ ├── pages/ # Page-level components (mapped in routes)
│ │ ├── app.routes.ts # Main routing file
│ │ ├── app.component.ts # Root component

[thomasdejaeghere]

This PR closes #11

[bramcomyn]

This PR closes #11

Fun fact, @thomasdejaeghere, you can also define this at the right-hand side of your screen by selecting issue #11 in Development!

[thomasdejaeghere]

This PR closes #11

Fun fact, @thomasdejaeghere, you can also define this at the right-hand side of your screen by selecting issue #11 in Development!

I was in fact searching for that functionality! Thanks!