armitage35 / day2day Goto Github PK

Current behavior
Tasks currently support break line in textual comments but they will not get displayed in the comment section.

Expected behavior
If the users want to use break line in comments, the app needs to display those.

Current behavior
Right now it is not possible to edit the name of a task

Expected behavior

• Display the task's name in the comment modal
• Add a tool to change the name of the task from this part of the site
• Save the edits made to the task's name

On completion, change the task completion property to TRUE
Only display tasks for which completed === false

Expected behavior
If there is nothing to be added, cliking on "I'm done" should just close the modal. In other words, only make the "if empty check" when the user hits enter to submit the task

Current behavior
Users can sign up and in and then they get their userID in a cookie and we roll from there.

Expected behavior
Let's finish things cleanly and use passport's cookies to save user id in a hashed way and save those in the db. Really, the gain is that we won't be giving the user his user id

• Generate a hashed id in a cookie comprised of the user's id that will then be used by the app
• Rather than handling redirections from the client (if the user is not logged in), do that from the back end (since jquery waits for the DOM to be ready this is not as clean as it could be)
• Save sessions in the DB

YouTube help

Expected behavior
Using passport js, enable users to create an account for D2D. Request access to

• Avatar (probably means we have to move gravatar to the local strategy)
• Calendar

Doc: https://developers.google.com/identity/sign-in/web/sign-in#before_you_begin && https://developers.google.com/identity/sign-in/web/backend-auth (where you use postman to check, don't try the lib)

Add a button that will display a drawer where the user can add one (1) comment to a task

Using this lib, implement a cool checkmark feature: https://codepen.io/north-of-rapture/pen/rWqega
🥇

Redesign the app to follow the following wireframe

Current behavior
Tasks are only DOM objects.
No date can be assigned to a task

Expected behavior

1. Tasks should be JS objects
2. Task list should display those objects

IF userTask.lenght === 0 THEN display a button to add a demo and trigger the onboarding

Rather than running on express 3.21, upgrade to 4. Read O'Reilly to know what changes

Now that we have comments, enable users to add Giphy reactions! A.K.A implement Giphy API

Current behavior
To reproduce

1. add a task
2. add a textual comment
3. it will add the comment and an undefined value

Expected behavior
Adding a comment should add only one comment: the user's and not an undefined value

Add comment code present twice

• Find today
• Refactor dates throughout the app
• Remember what view the user selected
• Go trough all tasks when displayed
• Group tasks by date
• Only display tasks that match the selected condition
• update CSS of selector

Careful: some tasks have no due date!

Add https://github.com/daneden/animate.css/blob/master/README.md

Current behavior
MongoDB saves newly created tasks but does not care about task edition.

Expected behavior
Mongo must update tasks when

• a task is completed
• a comment is added to a task (gif or text)

Method

• Upon task creation add the mongo id to the task.

Something needs to link the UI and Mongo so that we know what mongo object we're looking at
When an object is updated both the Task and the User Task need to be updated

fixed it by adding mongo's id to the object and I get to it by using the client's ID

Current behavior
Since Issue #42 a user can now sign up to Day2Day and create tasks that will be linked to his account. That is cool but so far he's still not able to access tasks from another computer.

Expected behavior
Using passport (http://www.passportjs.org/docs/), enable a user to sign up with his email / password

• Create a sign in page
• Send the sign in info to the server
• On the server, compare received information to DB info
• Display login error messages
• Give access to Day2Day and update the cookie (in case the computer is used by one or more person)
• Display user's tasks.

Expected behavior
Remplace the current modal for this baby:

Make sure that with this interface one can

• See his comments
• Create new comments

1. improve style
2. hide until hover

Current behavior
Issue #48 created the new UI. It's now time to make it work.

Expected behavior
Handle the following features

• Display the user's specific tasks
• Enable user to complete tasks
• Enable user to add task (until issue #51 arrives, just go for a modal)

DO NOT BUILD

• Any of the commenting features.

Screenshot

https://codepen.io/shshaw/pen/WXMdwE/

Duplicated by issue #55

Current behavior
We now have an app that handles users, tasks and comments. It looks aweful. It's time to get back on the front end saddle.

Expected behavior
Design what Day2Day will do and write in full letters how it'll be better than momentum. Write down all the requirements the app will need to reach the beta status.

Requirements in order
As a user i want to

1. See nice pictures
2. See date, time and weather
3. Handle to do
4. Handle notes
5. Handle pocket read list
6. Handle agenda

Design research
GDrive link

Requirements

1. The input to create new tasks should be moved within a bootstrap modal
2. This modal should be operable both by the material button AND by a keyboard shortcut

Send JS object tasks into a cookie file stored on the user's machine

Default tasks on request

Current behavior
Right now the app can only run the client side on GitHub but the server and DB can't.

Expected behavior
In order for user to be able to use the app decently, we need to run the app on cloudfoundy or AWS so that user's tasks can be saved.

• Deploy app
• Enable access trough SSH in C9
• Document deployment on digital ocean

Deploy on AWS: https://youtu.be/qZa5JXmsWZs

Some parts of the code are ugly to look at. Refactor

• cookie handling
• task counter
• what real use for the class creator since i create but one array ?
• make a choice between simple and double quotes

Current behavior
When looking for a gif and adding it to the task (or not adding it), the gif stays in memory and adds it to the task whereas it should actually be empty.

Expected behavior
Whenever the giphy is added or changed or whatever, REMOVE it from memory

Current behavior
Tasks are not fetched form mongo

Expected behavior

• Make a mongoose Scheme to save user info
• Assign an ID to each visitor
• Save this ID in a cookie
• Copy the ID in mongo
• If visitor already has an ID, don't create a new one
• Specify visitor ID in every task they create
• Fetch tasks accordingly to this visitor ID
• fill up user tasks with content of response
• Disable user task cookie (comment it)

Current behavior
Our current UI, while decent is not going to cut it for what we want this app to do.

Expected behavior
Build the foundation of Day2Day's beta. This screen will include

• A section to display a name and an email
• Some space for a gravatar
• The tool bar in the extreme right hand side corner (upgrade to FA 5)
• A place for date & time
• A place for weather
• An empty section where we'll later display tasks.
• A main picture taken from Unsplash (random on nature) with the name of the photograph
• Bring the modals too
• Bring the js function that handle UI stuff (toggles...)

DO NOT BUILD

• The task section itself
• Logics for date & time
• Logics for weather
• The logics to pull the gravatar

Screenshot

When you remove a task, the coloring will not budge

Solution 1) count the amount of task, divide by two and count again
Solution 2) review UI

Current behavior
Todos are only saved in the browser's cookies and that is cool but it's not the best thing to go towards a DB

Expected behavior
In order to move toward user handeling, the app needs to save todos in a JSON file in the server.

Current behavior
All request are answered with a 200 status code (provided that they worked)

Expected behavior
The API should send not only a response but also use the correct status code.

dev hint
Use the method res.status before the res.send

Current behavior
Since Issue #41 we now know if a user has already used this browser to access Day2Day. We now need to enable him to access his / her task on any device and browser he / she wants to use.

Expected behavior

• Verify if the user's already logged in
• Make a sign up page (reuse from https://codepen.io/alexdevero/pen/vNRqLL)
• If not display the sign up page
• Send the form info to the server
• On the server check that the information submitted are OK (required fields + format)
• Save those infos in mongo
• Redirect user to Day2Day app page
• Grant access to the user and set his cookie to his user id
• If the info are not valid, send a warning to the client (req.flash??)
• Display potential registration errors in the UI
• Check that this email is not already taken by another user
• If user has cookie and accesses /auth.html send him over to tasks
• Make sign up page responsive using bootstrap
• Add a cool registration successful animation
• nice to have: hash the password so as not to save it in clear text (https://www.abeautifulsite.net/hashing-passwords-with-nodejs-and-bcrypt)

Current behavior
Mongo is only used to copy tasks but is never called to load tasks

Expected behavior
Each user must have an id that we save in a cookie.
The user must enter his email. If the email exists in Mongo, pull his data, otherwise, generate a new ID
The user ID needs to be random and associated to the tasks he's going to create

Current behavior
Tasks are saved but nothing states what user they should be assigned to.

Expected behavior
A user should only act upon tasks he himself created. To do so we will need

• Create a diagram to explain what needs to happen

• Add a calendar widget in the input modal (add a calendar icon that expands into a complete calendar)
• Send the added date to the object
• Display this value within the UI
• Handle look & feel