-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve Authentication Issues #169
Conversation
Good riddance. Thanks!
|
NP! |
|
||
mongoose.connect(secrets.db); | ||
mongoose.connection.on('error', function() { | ||
console.error('MongoDB Connection Error. Please make sure that MongoDB is running.'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect this entire patch was prompted in order to remove this >80-char line. ;) 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😉 That .. and not a fan of storing OAuth tokens and user email addresses if we don't have to.
Tested sign-in sign-out. Works for me. I left a couple comments in code, nothing critical. Yay! |
Resolve Authentication Issues
This PR makes some major changes to the way authentication and sessions are managed by the application. In general, the goal was to simplify the codebase to work exclusively with Github authentication and reduce dependencies. This was acomplished by removing boilerplate, moving to client-side session storage, and eliminating the need for a backing datastore.
Revisions
require
-ed in the app itselfnpm test
that includes style and basic route checksResolves