Skip to content
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

Users / login feature #14

Open
papistan opened this issue Sep 28, 2017 · 6 comments
Open

Users / login feature #14

papistan opened this issue Sep 28, 2017 · 6 comments

Comments

@papistan
Copy link
Owner

papistan commented Sep 28, 2017

Problem - We cannot add additional user-focused features ( for example: custom deck feature, missed cards deck, email yourself missed questions) until we have user capability. Therefore, we need database, user model for account, and signup, login / logout views.

Potential solution
A user may sign up, login and out and have account for storage of their custom decks, etc once features built.

  • User model in node (email, username, encrypted password ).
  • Login / logout at top right of screen. When logged out, login/signup button shows. When logged in, username shows.

Note on design: I have not created a user feature with ReactJS or Node (only react-native with Firebase for user accounts), so I'm looking for someone who has experience or willing to explore to best advise on design.

@harshcrop
Copy link
Contributor

Hello, can you give more explanation on this soi can start work on this.

@jattoabdul
Copy link

i would also like to join in on this, as soon as there is better context to your request. Please give a more detailed explanation of the problem statement and your proposed solution to be implemented.

@papistan
Copy link
Owner Author

@jattoabdul @harshcrop thank you both! That would be great. I will edit comment above with more thoughts on problem / solution

@papistan
Copy link
Owner Author

papistan commented Oct 3, 2017

@jattoabdul @harshcrop any progress on this?

@papistan papistan closed this as completed Oct 6, 2017
@papistan papistan reopened this Oct 6, 2017
@urianchang
Copy link
Collaborator

@papistan would you be open to splitting this issue into smaller tickets? Maybe keep this one for the frontend work needed for user login and registration. The other tickets should revolve around the backend API like routing and database structure and management.

I'm willing to work on laying down the foundations for this request, so other people can work on it later. Anyways, let me know what you think. Thanks!

@papistan
Copy link
Owner Author

@urianchang this is a good suggestions and I would definitely be open to that. My backend background is in rails (currently learning node) so it would be great to see how this works and I need help to create clear direction for smaller tickets. If you could help with that I would really appreciate it. Please submit issues as you see fit and let me know how I may help in the process. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants