Open jyztintan opened 5 months ago
This is a very simple check which does not inconvenience the user, since with this error message, as long as users key in a positive number, the issue would be the latter. If the user key in a negative number, it should be clear to the user that the issue is the former.
Team chose [response.Rejected
]
Reason for disagreement: The current error messaging within the application lacks specificity, which can lead to user confusion and inefficient troubleshooting. The command takes in an internship index, and a task index. However, the same error message is returned during the 4 following scenarios:
Negative internship index, positive task index
Outofbounds internship index, positive task index
Valid internship index, Negative task index
Valid internship index, outofbounds task index
Negative internship index, Negative task index
Outofbounds internship index, outofbounds task index
This ambiguity forces users to verify two separate inputs—the internship index and the task index, and check for two separate conditions for its validity in each input-- positive number and not out of bounds.
This could inconvenience users as they have to check which is the applicable error.