Login integration #156
Merged
Login integration #156
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
login_pr.mp4
I updated the login page to be able to receive tokens and store them as a cookie in the browser. Currently, the website doesn't do anything with these cookies, and it provides the user no feedback as to whether or not their login was successful. You can test these changes by looking at the developer console in your browser of choice. There's only one valid account in the database for this PR: The email is "garvina@oregonstate.edu" and the password is "hunter2" (no, not my real password.)
I had to add a new dependency: js-cookie. Prior to running this program, you should run the "soft_restart" command in the shell.
Closes #152
Closes #130