In order to avoid changes in sub-tasks order while adding them, it's better to sort them based on something other than name.

Also cover updating and using the full potential of the sub-task's features.

• GitHub actions.
• CircleCI deployment.

Config ad in the app. A NONE ANNOYING ONE!

• View.
• Edit.

• Sign up.
• Sign in.
• Reset password.

Use GraphQL code generator when gql is updated!

Store latest used email and password locally, and fill the corresponding input fields with that value to make it easier for users to log in when they're is logged out.

Consider using optimisticResult and Subscriptions.

This should be tackled after #20.

A Task can have several tasks or nothing(standalone one)
If a parent task is marked as done, all the children will be marked as done as well.

For example:
Task project has 3 other sub-tasks: write documentation, write code, write test.

🟩 Project
    🟩 write documentation.
    🟩 write code.
    🟩 write test.

We can have it like:
🟩 Project
    🟩 write documentation.
    ✅ write code.
    🟩 write test.

or
🟩 Project
    🟩 write documentation.
    ✅ write code.
    ✅ write test.

And
✅ Project
    ✅ write documentation.
    ✅ write code.
    ✅ write test.

Task in database:

let users use the app without forcing them to sign up.

A category contains X number of tasks. Category is like a type/tag, it shows of what type a task is.

Like work indicates the tasks that are related to work.

In UI we can show/filter tasks of a the day by category, something like this:

So we save some information about the category in database.

Design some color schemes.

When we mark a task as done, all the sub-tasks(from sub_tasks table) will get a true value for their completed column.

Although it would be cool that this value be saved and then if user deselect the parent task(from tasks table), we reassign their old values again.

In categories, show/filter showing tasks of that category and group them in dates.

Daily, weekly and yearly view of tasks.

Add a free and paid flavors and configure the platforms.

In case of failure, guard can not get the issue and it fails!

• Add permissions to storage.
• Update production database.

The view that shows the today's tasks!

tasks and sub_tasks are as follow:

sub_tasks

tasks

Add Melos for the project.

The views for CRUD action for categories and tasks.

• Add a feature that can remind user before an event.
• Send some general notification to users.

• #19
• #21
• CRUD for them.