Open RyanQiu1 opened 1 year ago
As this does not hinder the user in any way, we feel that a task marked as a certain status is allowed to be marked again.
(In a sense show that it is done and the command user inputted is just a duplicate)
We feel that it would not matter if the command is a duplicate provided it does not hinder or confuse the user, since the outcome is still the same. We feel that having an error message to say that the task has already been marked with a certain status would give the same effect as our current implementation as simply letting them know the task is marked as a certain status.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
For tasks already marked as late, the error message still shows marked, perhaps an error message can show as task is already marked as late (In a sense show that it is done and the command user inputted is just a duplicate), to indicate that it is not changing. However this is a very minor featureflaw.