#To-do application structure
1 messages · Page 1 of 1 (latest)
<@&987246584574140416> please have a look, thanks.
It seems a bit strange to me. Why are todos linked to a section, and not a project (or even better, a task)?
How do you differ between user and todo tags? A user is not linked to a todo tag (so a user is not working on one/assigned to)
I'd give a todo a nullable parent todo so you can nest, rather than sub todo
...
Can you give some more context for others?
will do the parent todo
and thing about section is that projects will have different sections that consist of todos
i use todoist to stucture my project
what do u think is it better to do like this: having todo list in user entity itself or it is kind of weird?
tag list in user is for that uses can have their own tags and category too
what do u think?
so, u are saying that it is better to have user_id in todo tags instead of having tag list in users. yeah?
I'd expect a user to have a to-do list, which contains of multiple (sub)tasks. Each task has one/more tags.
A task can potentially belong to multiple projects in my opinion
My advice is: before drawing out the diagram, try writing the flow out/try your flow yourself.
ohh, i didn't think about it
can u tell it in easier way
my english is not sooo good
As in: don't start from trying to draw the diagram, but instead just write the process out.
Then things like: 1 todo possible being for multiple projects pop out
okay, thanks)