adastros / do-it Goto Github PK

New and in-progress tasks for projects will only be displayed if a user clicks to view the project. It should be not be displayed when viewing Inbox, Today, and Upcoming. Task data should be save to the associated localStorage key, not in taskData.

Completed tasks will be handled in a different issue.

There should only be one "Add task" button in task viewer at a time. Canceling an edit action for a task item should not create extra "Add task" buttons. This bug seems to have occurred sometime after commit # 1add4f0.

The feature should be optional when creating a task item and indicate multiple levels of priority. Task priorities should be editable by the user and displayed under the task header and description.

This update is make the iconButton more reusable and standardize it's use across the application. It will accept an image and alt text as argument but the css classes will be fixed. Components using the iconButton component will need to be updated to use the new component.

The small icon button will be a reusable component with fixed classes. The icon will accept an image and its alt text as an argument. The css class will be fixed.

This is due to the width of the container not expanding to fill the empty space of the page when the menu bar is closed.

There should be at least seven boards (one for each day) with a title that displays the current date and the next 6 days.

Currently, adding a new project only creates a new tab on the menu bar with the title of the project. Adding this functionality would help provide a form of indication of what project is currently on the screen.

Tasks should be loaded onto secondary task boards. Each secondary task board should be titled with the due date of the tasks and sorted from the earliest to furthest date. This is so that overdue tasks are shown first with tasks that need to be done later are shown last.

This section will house elements such as the tasks, dates for the task, a header indicating what is being worked on, etc.

This will require a refactor of how new projects are saved to localStorage. This issue was created to minimize name space pollution in localStorage and make finding relevant data easier.

Editing a task and saving it should update the browser local storage with a new ID and remove the old one.

Cancelling a task while editing it should not create a new key value pair. The browser local storage data should remain the same.

Canceling an edit action for a task item should discard any changes made to task header and description.

The value of the local storage key should be an empty object.

The task is duplicated on the DOM but is not duplicated in localStorage. This does not affect the new project or task forms.

After working on this issue, it would be much simpler to use the app if there is one add new button at all times. This will simplify the interface and make the code less complex and easier to maintain/ build upon

When clicking through the different tabs, the apps should parse the json file to list the relevant tasks for the tab.

Tasks are uncompleted by checking the checkbox. Doing so should remove the tasks from the completed key in localStorage and copy them back to the appropriate place in taskData. Uncompleted tasks should be visually shown on the DOM when switching between the Inbox, Today, and Upcoming menu tabs.

This will require a refactor of how tasks are saved and retrieved from localStorage. Refactor of some taskController functions are required since the functions used to interact with localStorage is shared.

The due date text in the task form wraps onto a second line. This is due to input is set to width:100%. The css styles for other components will need to be refactored if the styling for the input tag is removed.

Sorting should only occur when a user clicks on the Completed menu tab. Adding a new task should not add it to the DOM when a user is viewing completed tasks.

Prior to deleting a task, an overlay prompt should appear to confirm that the user wants to delete the task.

Users should be able to edit any tasks whether they are completed or not. The edit function should be facilitated through a button without having to dig through a secondary menu.

The icon button will be a reusable component with fixed css classes. It will accept an image and its alt text as arguments. The css class will be fixed.

This is to prepare the app for upcoming features. One such feature involves sorting tasks based on the tab clicked on the menu bar.

The edited task will be removed from view and won't appear until the page is refreshed or the user clicks to another task view.

The completed key should store all relevant information for a task and group them based on the completed date. Completed tasks should be deleted from the taskData key and copied over to the completed key.

Task ID should be not linked to the due date and task # created. If a user decides to change the due date for a task, the created ID will no longer match the updated task due date and task #. Updating the task ID to match the updated due date and task # isn't the best solution and will make the code base a more complicated since the ID can change constantly and needs to be tracked.

For example, if a task was created with a 'low' priority tag, editing the task would show the priority as 'none' instead of 'low'. This would inconvenience the user since they would need to constantly change the priority back the level they wanted. Users could also miss the change resulting in unintended priority changes.

Using the web storage API, store tasks and relevant data to a user's browser's locale storage. Local storage on chrome can be viewed by accessing the browser's developer tool, going to application, and looking for "local storage".

New tasks should be added to either a corresponding date board on the primary task board or new date board if the date board doesn't exist. New date boards should be inserted into the primary task board based on its date.