-
Notifications
You must be signed in to change notification settings - Fork 5
Deliverable 2 Report
Elie-Elia edited this page Dec 30, 2019
·
9 revisions
- We decided that in order to verify a user, a user role should be attached to it. Whenever a user would then have a user role, we set the isVerified boolean condition to true.
- In most of the CRUD methods, we decided that it would be best if a complete object of that class was passed as an argument, and an another object would be returned.
- For the update methods, we decided to delete the old instance of an object and create a new with the new information in the repo, as the class CRUDrepository doesn't contain any update method.
- Overview of project deliverables
- Breakdown of methods to implement for each class
- Assigning issues to every method
- Assignment of tasks:
- Karl Eid: Tutor, Lesson, Payroll + Project Management
- Preyansh Kaushik: Reviews, Get Reviews for a specific user, Subjects, Manager
- Elie Elia: Student,Room, University
- Nicolas Abdelnour: Course, UserEntity, Schedule
- Discussion over the different methods to implement
- Discussion over the issues encountered
- Design choice:
- Instead of finding tutors, managers and students by their auto generated id's, we're gonna find them by their linked user emails
- User is seen as verified if it has an associated UserRole