Open bsoe003 opened 9 years ago
I think we need to plan out how the structure of the app is going to look for this.
Are we going to have separate views independent of an event or are events going be the driving force? i.e. the only views we support are events and user can associate themselves with the event.
IMO, I think we should have a structure that looks like this
/ => allows an organizer to set an event /q/:qid => homepage for event. If user is not authenticated then they are prompted to sign in, otherwise if they are then show the queue
Thoughts?
we can probably have this setup: / => where organize sign up /login?origin=[either qid or home] => for login view (if origin query is invalid then just use home) /q/:qid => queue page that checks auth. if not auth then redirect to above route.
sgtm
As of now, Facebook OAuth 2.0 in backend is handled by Passport.js library. However, we still need UI components to allow users to login using their Facebook credentials. For example, a button to login and a button to logout.
Two routes that are associated with this task are:
It may throw an error by Facebook when attempting to authenticate as only designated URL can be used for OAuth.
PLEASE MAKE A SEPARATE BRANCH FOR THIS.