No error thrown for single-digit INDEX with prefix "0" for delete

[Javiery3889]

Describe the bug

The UG currently states the following for the delete command:

If the user enters a single digit INDEX with a prefix string of "0" prepended, the command still runs successfully.

Steps to reproduce

Assume that the list has at least one person
delete 0000000001

Expected

Throw an error for invalid INDEX

Actual

Person at index 1 is deleted successfully

Suggested fix

Perhaps it would be better to reject such instances and throw an error for invalid index instead

[nus-pe-script]

Team's Response

Thank you for the issue.

By intuition, 1 equals 000001 and so on. Hence inputting “0000001”, or any number of leading “0”s does not change the fact that it is still an integer, and its value is still 1.

Hence as long as there is a valid contact at index 1, the app will treat the input as valid and correctly delete the contact.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: Thank you for your response!

While I do agree that the intuition of having an INDEX appended with a string of 0 will be treated the same, I felt that this behaviour was not highlighted in the UG and might cause some users to be unaware of this beaviour. Perhaps it would be better to explicitly state this behaviour in the UG, similar to the behaviour of extraneous parameters for commands which was documented in the UG.

Because of this, I would categorise this as type.DocumentationBug instead with the same severity of severity.Low.

---