[Feature]: Blockers #3

New Issue

2024-05-05T15:13:10Z

tristonarmstrong commented

2024-05-05 15:13:10 +00:00

(Migrated from github.com)

Guidelines

I agree to follow this project's Contributing Guidelines.

Description

Would be nice to know if a particular task has any outstanding blockers.

Problem

I dont know if a task i have planned for the day can be worked yet or not

Proposed Solution

each todo likely needs to hold more information than just the string value of what it is. Maybe a status which could be indicated in the ui, as well as some way to set a blocker. Blockers will probably need to be their own struct as well.. Tho, if i were to make it super simple, id say something along the lines of this COULD suffice in the short term:

struct Todo {
    blocker: Option<String>
}

then if blocker is not None then one could assume theres a blocker and display it somehow. Youll ofcourse need a way to display it. Maybe a modal will suffice?

This will ofcourse mean just 1 blocker per todo.

Alternatives Considered

A more complex approach ofcourse. A status on Todo and a list of blockers with some visual representation. Blockers could hold a value and a status of themselves maybe. Could be a V2

### Guidelines - [X] I agree to follow this project's Contributing Guidelines. ### Description Would be nice to know if a particular task has any outstanding blockers. ### Problem I dont know if a task i have planned for the day can be worked yet or not ### Proposed Solution each todo likely needs to hold more information than just the string value of what it is. Maybe a status which could be indicated in the ui, as well as some way to set a blocker. Blockers will probably need to be their own struct as well.. Tho, if i were to make it super simple, id say something along the lines of this COULD suffice in the short term: ```rust struct Todo { blocker: Option<String> } ``` then if blocker is not `None` then one could assume theres a blocker and display it somehow. Youll ofcourse need a way to display it. Maybe a modal will suffice? This will ofcourse mean just 1 blocker per todo. ### Alternatives Considered A more complex approach ofcourse. A status on Todo and a list of blockers with some visual representation. Blockers could hold a value and a status of themselves maybe. Could be a V2

Sign in to join this conversation.