Open shamesjen opened 6 months ago
Thanks for pointing it out! The third line of the error message specifies that INDEX must be a positive integer. -1 is a non-positive integer, so the team feels that the error message provides sufficient warning.
As seen in the given PE information website, editSeller 210000000000000 n/savage
is an extreme user behaviour, which is not considered a bug as stated in the website.
https://nus-cs2103-ay2324s2.github.io/website/admin/tp-pe.html#functionality-bugs-2
Team chose [response.Rejected
]
Reason for disagreement: You already have an error message that specifies the index is wrong, the fact that it is not throwing the error message that it should already indicates a bug.
The error message currently thrown is telling the user the format is wrong, the definition of format being
In this case, the user would be confused as to why the format is wrong, which is not what the dev team should be intending to happen.
Description
Referring to the images above, the first image is expected behaviour of the error messages. The other two messages say that the format is wrong when the format is correct but the index is wrong.
Steps to reproduce
editSeller 210000000000000 n/savage
.Expected behaviour
At step 2, output should be the same as step 3.
Actual behaviour
At step 2, output is different from step 3.
Reason for severity
A user may be confused on why the format is wrong and might not be made aware the index is the one causing the issue.
Ideas
Check the error handling and use the error thrown for Step 3 / the first image.