Releases: obsidian-tasks-group/obsidian-tasks
0.8.3
Changes
- Tasks now actively checks that you toggle a task in a markdown file.
- Only files with the file extension
.mdare allowed.
- Only files with the file extension
0.8.2
Changes
- Query results are now re-rendered after midnight (#107)
- Toggling a task now keeps the cursor position
- You can now set obsidian tasks' actions in the mobile toolbar (icon still generic) (#71)
- Fixed a bug where rendered results weren't updated when a file was renamed or deleted
Internal
- File updates now read from the file system
- Use obsidian's moment instead of bundling our own
- Replace all usages of innerHTML
- Switch obsidian dependency to packaged version
0.8.1
Changes
- Query results are now sorted first by status (todo before done) (#83)
- Fixed a bug where a query would still list tasks from a file if the file did not include any list elements anymore (#86)
- Fixed a bug where a task could sometimes not be toggled (#87)
- Styling is now easier since
ul(query result) andli(everywhere) elements of tasks have specific classes (#91)ul:plugin-tasks-query-resultli:plugin-tasks-list-item
0.8.0
Changes
- You can now limit query results to a specific number of tasks (#76)
- You can now filter query results by heading (#35)
- You can now use relative dates in your query filters (#1)
This is an example of what is now possible:
```tasks
not done
due after yesterday
due before in two weeks
heading includes task
limit to 10 tasks
```
Meaning “the first ten open tasks that are due within the next two weeks (starting today (after yesterday)) and where the heading includes task (for example ## Tasks)”.
See the README for all the details.
0.7.0
Changes
New command to open a modal to create or edit a task.
You can bind the command to a hotkey to quickly create or edit tasks in the editor.
0.6.4
0.6.3
Changes
Fixed pluralization of task count at end of query results
0.6.2
0.6.1
0.6.0
Changes
Tasks now supports recurring tasks 🔁 🎉
Recurring tasks (repetition)
Tasks can be recurring.
In order to specify a recurrence rule of a task, you must append the "recurrence signifier 🔁" followed by the recurrence rule.
For example: 🔁 every weekday means the task will repeat every week on Monday through Friday.
When you toggle the status of a recurring task to anything but "todo" (i.e. "done"), the orginal task that you wanted to toggle will be marked as done and get the done date appended to it, like any other task.
In addition, a new task will be put one line above the original task.
The new task will have the due date of the next occurrence after the due date of the original task.
Take as example the following task::
- [ ] take out the trash 🔁 every Sunday 📅 2021-04-25
If you mark the above task "done" on Saturday, the 24th of April, the file will now look like this:
- [ ] take out the trash 🔁 every Sunday 📅 2021-05-02
- [x] take out the trash 🔁 every Sunday 📅 2021-04-25 ✅ 2021-04-24
For best compatibility, a recurring task should have a due date and the recurrence rule should appear before the due date of a task.
Right now there is no direct feedback to whether your recurrence rule is valid.
You can validate that tasks understands your rule by checking that the task includes the recurrence rule when it is rendered, for example in the markdown preview of the file where it is defined or in another tasks query.
When it is shown (with the checkbox on the left), then tasks understands it.
Examples of possible recurrence rules (mix and match as desired; these should be considered inspirational):
🔁 every weekday(meaning every Mon - Fri)🔁 every week on Sunday🔁 every 2 weeks🔁 every 3 weeks on Friday🔁 every 2 months🔁 every month on the 1st🔁 every 6 months on the 1st Wednesday🔁 every January on the 15th🔁 every year