-
Notifications
You must be signed in to change notification settings - Fork 92
New support for subtasks #594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
If by cache you mean the cache database, it should be enough to just increment the schema version to force a rebuild. |
Taken from RFC 5545, section `3.8.4.5`. If present in a file, these values are now read and stored in the cache. Nothing in the UI has been changed. Tests are modified to reflect the change. Increment `SCHEMA_VERSION` to allow cache recreation on todoman update.
New names and values added to the JSON output for the `RELATED-TO` property.
List text output is now with a tree structure: task 1 task 2 task 3 task 4 task 5 The table list is changed to a dictionary representing a tree. No changes to the SQL queries are made. RELTYPEs PARENT, CHILD and SIBLING are supported. https://www.rfc-editor.org/rfc/rfc5545#section-3.2.15 Includes output space formatting fixes. Tests adjusted to changes.
Comment for describing the weird code for merging arguments.
Using the newly supported attributes, two new options are added. `--subtask-for`, making a task be a subtask for another and `--not-subtask`, making a task no longer be a subtask. The commands `new` and `edit` are fitted with these new options.
e87552a
to
b6ee7fa
Compare
Ah thank you, I totally missed it! I rebased my changes to make use of this and to describe it properly in comments and in the documentation. I edited the first comment of the PR to remove the "breaking changes" part since it's not true anymore. |
Add support for RELATED-TO property and RELTYPE parameter.
Taken from RFC 5545, section
3.8.4.5
. If present in a file, these values are now read and stored in the cache.Tests are modified to reflect the change.
The
SCHEMA_VERSION
is incremented to allow the cache to be recreated after the update.Nothing is required from the user to be done for the changes in this PR to work.
Before:

After:

Closes: #396