This might be a very personalized issue, but in case it is not - i would like to be able to separate tasks from checklists that might not have anything to do with tasks per se.
For example, i have a rather huge checklist of literature in my vault which tracks the books i read/plan to read. It makes perfect sense for it to be a checklist, but the app treats every book in this note as a task, which pollutes the tasks menu.
I think, it would be better for tasks to have their own special notation e.g. @TASK(*task body*) or something like that. Markdown's check boxes have a lot of use cases and treating them as a task-only thing seems to be a bit wasteful. It makes sense for a ZenNotes-specific task feature to have a ZenNotes-specific notation that would separate tasks from everything else.
This might be a very personalized issue, but in case it is not - i would like to be able to separate tasks from checklists that might not have anything to do with tasks per se.
For example, i have a rather huge checklist of literature in my vault which tracks the books i read/plan to read. It makes perfect sense for it to be a checklist, but the app treats every book in this note as a task, which pollutes the
tasksmenu.I think, it would be better for tasks to have their own special notation e.g.
@TASK(*task body*)or something like that. Markdown's check boxes have a lot of use cases and treating them as a task-only thing seems to be a bit wasteful. It makes sense for a ZenNotes-specific task feature to have a ZenNotes-specific notation that would separate tasks from everything else.