Open ondretann opened 6 months ago
Besides, because of the error section highlighting feature, it should be clear that the program is interpreting the whole 1 h/test
as the index.
NotInScope
because it would incur a significant additional implementation cost --- currently, the program only parse recognized prefixes.
Team chose [response.NotInScope
]
Reason for disagreement: Clearly, this bug should be in scope since the wrong error message is output.
When entering a wrong parameter prefix for an add command, the output error message seems to be misleading or wrong.
As shown above, since "h/" is an invalid parameter prefix, an invalid command format message should be displayed. However, provided message is that contact index is invalid.
This will cause users to spend an extra amount of time trying to figure out the error in their command input, and lead them to believe that the contact index "1" is invalid.