Inconsistent delete command error messages if index input is Long(>Max)

[Nihirraa]

Here the error message states that index should be within list size

If a long number is input, the error message changes
Expected error message: index should be within list size
Actual error message: invalid delete command format

[nus-pe-script]

Team's Response

We believe that these are acceptable error messages for each incorrect command.

The former uses a "valid" but "out of bound" index, i.e. index is larger than number of persons in the list, such as delete 20 when there are less than 20 persons. In this case, we made the assumption that the user does in fact understand the command, but merely made a mistake when entering the index, therefore providing a more specific error message with information on the number of persons in the list can assist the user in picking a correct index.
(the list size has unfortunately been cut off by the UI, but can be accessed by expanding the UI or by scrolling to the right)

The latter uses an "invalid" index, e.g. an unreasonably large number or a zero index, such as delete 376421876437637641 and delete 0. In this case, we argue that the user has a fundamental misunderstanding of the command, therefore requires a "Invalid command format" error. This error clarifies what the command is and the information that it "Deletes the person identified by the index..." is useful in the case that a user is typing numbers that don't make sense.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: Both cases involve invalid indices and should result in a consistent error message, as differing responses can confuse users. Even a large number could be a typo, and providing an "out of bounds" message with context (e.g., "Index must be between 1 and [list size]") would help users correct their input without assumptions about their intent. If large numbers are truly considered invalid, this limitation should be clearly documented in the user guide to avoid ambiguity. Consistent error handling improves usability and clarity.

---