[x] Implement landing page with a login button somewhere or go straight into the login/register path
[x] For the registration page, first send a GET request to /api/registration/programs to retrieve colleges and respective majors. Hit the endpoint in the browser first to view the structure. Store in an object.
[x] Form should collect
Name - the name of the user signing up
Email - the @auburn email address of the user signing up
Password - the plaintext password the user has selected
Major Id - from the major selected in the dropdown, send only the id associated with it
Sections - from the sections on the dropdown, send the IDs of every one of the ones selected
[x] When the name textbox loses focus, send request to api/registration/validate with query parameter available equal to the email address that was just typed. The response will let us know if the user already exists in the database and if they should be added again. The response will be json in the form:
{ 'available': boolean }
[x] Depending on the college that is selected, the majors should update accordingly on the dropdown.
The registration data should be a POST request to /api/registration with the exact names:
name
email
password
major_id
sections[]
If successful, the server will reply with:
{ publicId: string }
which corresponds with the profile id that was just created.
Deletion has not yet been implemented, so for testing, use different email addresses every time, or the request will fail. Postman is highly recommended for this
cadomani
commented
2 years ago
{ 'available': boolean }The registration data should be a POST request to /api/registration with the exact names:
If successful, the server will reply with:
{ publicId: string }which corresponds with the profile id that was just created.
Deletion has not yet been implemented, so for testing, use different email addresses every time, or the request will fail. Postman is highly recommended for this