Closed ratchet12340 closed 6 years ago
As we are refactoring a lot of the server side to use new models and such, we will look to split the User model into two models:
For reference, this is the preliminary model in mind:
- user_id (ref) - project_id (ref) - semester_id (ref) - rin (string) - credits (string) - status (string - student, external mentor, alumnus, RPI faculty, etc.) - schedule_conflict (boolean) - has_completed_urp_form (boolean) - requires_wheelchair_accessible_room (boolean) - mentor_preferences ([ref])
For this issue, please make the rudimentary UserRegistration routes. This will entail making the index.js file like before. We will have the following routes implemented, so please define matching functions in the UserRegistration controller.
index.js
GET /api/user_registration
POST /api/user_registration
GET /api/user_registration/:userid
PUT /api/user_registration/:id
DELETE /api/user_registration/:userid
Resolved
As we are refactoring a lot of the server side to use new models and such, we will look to split the User model into two models:
For reference, this is the preliminary model in mind:
For this issue, please make the rudimentary UserRegistration routes. This will entail making the
index.js
file like before. We will have the following routes implemented, so please define matching functions in the UserRegistration controller.GET /api/user_registration
POST /api/user_registration
GET /api/user_registration/:userid
PUT /api/user_registration/:id
DELETE /api/user_registration/:userid