Restructure Portal’s backend to de-spaghettify the code using modern frameworks and coding patterns. In addition to the clean data models, this will provide the clean data-access layer necessary for us to update Portal’s data queries and break the circular dependencies without affecting Portal’s frontend. Portal is responsible for managing 3 data models: User, School and Class. For each model, we will develop CRUD endpoints. The foundation of the data-access layer is already in place and just needs to be built on-top of.
Note: the Teacher and Student models are extensions of the User model that distinguishes the type of user; a user is a teacher if they have a teacher profile.
lauracumming
commented
2 weeks ago
Restructure Portal’s backend to de-spaghettify the code using modern frameworks and coding patterns. In addition to the clean data models, this will provide the clean data-access layer necessary for us to update Portal’s data queries and break the circular dependencies without affecting Portal’s frontend. Portal is responsible for managing 3 data models: User, School and Class. For each model, we will develop CRUD endpoints. The foundation of the data-access layer is already in place and just needs to be built on-top of.
Note: the Teacher and Student models are extensions of the User model that distinguishes the type of user; a user is a teacher if they have a teacher profile.