Longer term, maybe even todos will become a "post", making the code even simpler. They already share a lot of the same functionality like @mentions or being able to receive likes and replies etc.
Plus, I see people writing longer todos these days. Myself included. But we don't support line breaks yet. Don't see a good why we shouldn't allow that.
So "todo" could simply a special type of post.
Either way, that's something more long term. For now, adding posts to the feed seems like a good first step.
I think that a todo as a post makes sense. It's quite common for task managers to have a title for the task and a description, then you decide if you use only the title or both.
I like the idea of simplifying data models and not repeating functionality when possible. So, no reason a TODO couldn't be a post. I figure it's a bit of text, media, hashtags, at-tags, comment tree like everything else
The only difference I can see is that posts can have a topic like "Finance"
To avoid joins/for perf reasons, maybe just use a discriminator column and have a generic posts table with "type" being the discriminator (values "post" "todo" where "post" rows have the topic ID/name filled in and whatever else makes them unique; all other columns could be shared)
Longer term, maybe even todos will become a "post", making the code even simpler. They already share a lot of the same functionality like @mentions or being able to receive likes and replies etc.
Plus, I see people writing longer todos these days. Myself included. But we don't support line breaks yet. Don't see a good why we shouldn't allow that.
So "todo" could simply a special type of post.
Either way, that's something more long term. For now, adding posts to the feed seems like a good first step.
I think that a todo as a post makes sense. It's quite common for task managers to have a title for the task and a description, then you decide if you use only the title or both.
I like the idea of simplifying data models and not repeating functionality when possible. So, no reason a TODO couldn't be a post. I figure it's a bit of text, media, hashtags, at-tags, comment tree like everything else
The only difference I can see is that posts can have a topic like "Finance"
To avoid joins/for perf reasons, maybe just use a discriminator column and have a generic posts table with "type" being the discriminator (values "post" "todo" where "post" rows have the topic ID/name filled in and whatever else makes them unique; all other columns could be shared)