Open CShuwen opened 1 year ago
Thank you for the suggestion. Currently, our error messages are pretty short, in the form of either "invalid command" or "unable to parse input". Hence, we think that 3 second is enough for users to read the message. However, we do plan to make our error messages more specific, as mentioned in the planned enhancement
section of our DG, and we will take our suggestion into consideration.
Team chose [response.NotInScope
]
Reason for disagreement: Thank you for considering the suggestion. While it's true that your current error messages are short, it's important to consider that users may not always be able to read them within three seconds. Users may have different reading speeds or may be distracted by other things, such as notifications or background noise.
The error message disappear within 3 seconds after being displayed. Not even allowing the users to have ample time to read the feedback to them
This significantly worsening the usability and user experiences of the app