173 feature rough department and position onboarding page

[laurenbrissette]

Description

I created a new page called register that the user is rerouted to when either their department or position is empty. The page tracks their department and position selection, and when they click submit, calls back to AuthContext to register them. If either a position or department is already in the database, the respective field is disabled on the selection page. Submit is disabled until a position and a department have been chosen. As of right now, there are no restrictions on what combination of department and position a user can select.

Also, I added a function to the AuthContext interface to complete registration of a new user.

Motivation and Context

When MFA members log in for the first time, their email might not be associated with a department and position, but we need to enforce that they have this information to use the site.

Closes [#173]

How has this been tested?

I tested the rerouting and selection updates by temporarily forcing all users to go through Register and logging the selections and fetched data. I was able to walk through the onboarding process. I will note, I was testing through a northeastern.edu email, so I wasn't able to test the submit functionality (it relies on auth database and therefore is unable to find a northeastern user). However, this won't interfere with us logging in using northeastern emails as long as they are preinitialized with a position and department.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
mfa-form-automator	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 3, 2024 1:33am

[kaiyangzheng]

It looks like we won't be able to register an employee because userData, email, password, departmentName, and positionName will be null in register.tsx.

There is a way we can get around this by exporting that data from auth context or saving it in local storage, but the changes will take a while and I don't want to rush so we can discuss during GM.