handle the case where a user:
(A) did not complete an item, but
(B) wants to remove it from the task list
this is removing an item, but for a different reason.
we do NOT want to just remove the actual item from the data. I want this to be indicated in the data structure that it was deleted or canceled. So we'll probably have to put another status/state that tasks can be in, and the main list will filter them out specifically.
The reason for this: Often, I have to do list items that get added to my list, but then in a week or 2, it is no longer necessary. This isn't because I completed it -- instead, it may have just become irrelevant. I want to remove them, but I don't want to mark it "completed". And in the future, I'll want to see how often I am just "removing" items because they became unnecessary.
https://monosnap.com/file/vAPs9AeJxRM7izi1ENp8gJZw1tLgPI
handle the case where a user: (A) did not complete an item, but (B) wants to remove it from the task list
this is removing an item, but for a different reason.
we do NOT want to just remove the actual item from the data. I want this to be indicated in the data structure that it was deleted or canceled. So we'll probably have to put another status/state that tasks can be in, and the main list will filter them out specifically.
The reason for this: Often, I have to do list items that get added to my list, but then in a week or 2, it is no longer necessary. This isn't because I completed it -- instead, it may have just become irrelevant. I want to remove them, but I don't want to mark it "completed". And in the future, I'll want to see how often I am just "removing" items because they became unnecessary.
i'll use this for tracking purposes later.