GothenburgBitFactory / GothenburgBitFactory/taskwarrior
recurrence templates without IDs
- Dominant language
- C++
- Stars
- 6.1k
- Forks
- 423
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 11
Description
Hello there!
I suggest that recurrence templates no longer have IDs.
Since it is discouraged to interact with those anyways and because their ID isn't even shown in the info about child tasks I think it's both a risk for accidental modification or deletion of parent task and unnecessary. At least on my part interaction with those tasks happens through child tasks or UUID, never ID. Also a database with lots of recurring tasks would have less inflation of IDs as a small bonus.
It is not very important to me, just something I noticed recently.
If you decide to keep it as is, I wonder why child tasks info doesn't show parent task's ID.
Kind regards,
Jaker
Contributor guide
Assessment
This issue has not been assessed yet.