Skip to content
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

Add support for dependencies in tasks #568

Closed
tionis opened this issue Jan 18, 2025 · 2 comments
Closed

Add support for dependencies in tasks #568

tionis opened this issue Jan 18, 2025 · 2 comments

Comments

@tionis
Copy link

tionis commented Jan 18, 2025

RFC9253 introduces some additional RELTYPEs to the standard, one of them being:

RELTYPE=DEPENDS-ON:
This indicates that the current calendar component depends on the referenced calendar component in some manner. For example, a task may be blocked waiting on the other, referenced, task.

It would be nice to have support for that, as tasks often do have blockers and nearly no to-do apps consider this problem.
I'm not sure at the moment how that should look or work exactly, though.

@tionis
Copy link
Author

tionis commented Jan 19, 2025

After thinking about it I think it would be nice to be able to specify a list of tasks that need to be finished before in the edit panel (e.g. by specifying it's id, perhaps later an fzf style interactive selector?)
Show and list would also have to show dependencies somehow e.g. via something like @depends_on(1, 2) or whatever fits the current style best.

The main benefit would then be an integration into todo list --startable as only tasks for which all dependencies are done would be shown here (unless the task is overdue maybe?)

@tionis tionis closed this as completed Jan 19, 2025
@tionis
Copy link
Author

tionis commented Jan 19, 2025

Ups, wrong button.
Could some please reopen this, I don't have permission to do it.
Perhaps @WhyNotHugo ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant