fack1 / familia Goto Github PK

• Create EndPoints:
  GET: /joinFamily
• add family into families collection.
• update user's family_id to the new added family id.
• redirect to GET: /.

First test of the app, user testing results should be on the comments.

This Design:

• Add endpoints:
  GET: /auth
POST: /register

• collect user's data using DOM manipulation.

• send user's info from the client side via fetch to the server.

• hash password using bcrypt.

• store data in the database.

• set cookie for the response, and hash it.

• redirect to GET: /.

• I think need good
• its not clear in that place put it in part with big size

*Make File structure

• Linting (ESLint).
• Travis CI setup.
• Discuss Standards: naming conventions, ES-version.
• Build basic express server.
• Setup heroku app.
• Set and configure handlebars.
• Build the DB (MongoDB).

Should fix these bugs:

• Create new Account.
• Login
• authenticated user can access to the GET: /auth page, he shouldn't be able to get there.
• Other bugs should be added here!

• Create Endpoint GET: /
• Check if there's a cookies and if it's valid.
• if cookies is valid: check if user has a family_id.
• if user has family_id: response with the list page.
• if user doesn't have family_id, redirect to GET: /join.
• if cookies is not valid, redirect to GET /auth

• need work in design

• Create endpoint POST /addItem
• Send request with the form to the server.
• Check if cookies is correct.
• Add new item with family_id of user.
• redirect to GET: /.

Endpoint: POST: /login

• collect user's login data.
• send user's data to the server from the client side via fetch.
• on server's side: check if username exists, and check if their password is correct or not.
• if data is valid, set cookie for the response and hash it.
• redirect to GET: /.

• the user will not know if done or not in this case its the same page if done

This design:

• I like how to use .then to make code easy and simple .

This design, just without change family option.

Should create homeRoute which is GET: / to :

• Check cookies:
  - not found => redirect to GET: /auth.
  - found => continue.
• Check if cookie is valid:
  - Not valid => redirect to GET: /auth.
  - Valid => continue
• Use the SECRET key to get the id of the user

• Create GET: /settings router
• Create function to handle the route.
• Find the family of the user authenticated.
• Get the family key.
• Send the family key to the view to be rendered.
• Show the family key in the setting view page.
• Send rendered page to the client.

Second test of the app (after the 1st sprint). User testing results should be on the comments.

This design:

• Send family code using fetch.
• Check family code if exists.
• if id exists, Update user's family_id to the existed one.
• if it's not exists, response with error massage.