Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Incorrect error message for invalid task index

Steps to reproduce:

edit 1 -ti0 -tnDrink Milk

Expected: Error message: Invalid task index

Actual: Error message: Invalid command format

_{[original: nus-cs2103-AY2122S1/pe-interim#3281] [original labels: severity.Low type.FunctionalityBug]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Our format stated that the parameter for -ti is a POSITIVE INTEGER. It is explicitly stated in the UG as well as the error message. Hence, using 0 for the parameter of -ti is considered as an invalid format as 0 is not a positive integer to begin with.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

[x] I disagree

Reason for disagreement: From the website, the requirement for duplicates are as follows:

The team did not indicate in any way how this bug is caused by the same defect and cannot be solved independently.

:question: Issue response

Team chose [response.Rejected]

[x] I disagree

Reason for disagreement: Copied from my response to the duplicate bug:

While we can argue on what it means to have an invalid command format, the fact still stands that the error message is not very intuitive. Saying incorrect command format does not exemplify to the user what is wrong with their command. Incorrect command format can mean a typo in the flag, a typo in the command word, an invalid index, etc. This causes minor convenience to users who are still new to the command's format. This issue is also exemplified in the module's website as shown below:

As such, this issue is more of a feature flaw than a functionality bug, but it remains as a bug of low severity.

tanjiaxian99 / pe

Received invalid command format when INDEX == 0 #3