Open edelinetenges opened 3 years ago
The error message is clearly a preference of the tester, but does not impact the functionality or features of our application.
The description is supposed to be a field where the user can add a small note, such as the deadline, or any other dependencies of the homework they have, such as which chapters it's related to, etc.
We do not believe it is a valid argument to input a task into Focuris but not have time to type in a short description for a task.
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your reason]
Busy university students who are rushing to input events into their app would want to do it as quickly as possible, but making the description field compulsory slows them down and might even be redundant since students usually condense their events into one phrase.
I understand that it is clearly stated in your UG, and it could be because I was careless and rushing, but it took me a while to figure out why my following command could not work. However, considering how your target users are probably rushing as well, perhaps it would be good to include a more meaningful error message.