Open nus-se-script opened 2 weeks ago
Thanks for bringing up this issue about unclear "tag names" error messaging. You're right that we should display a more user-friendly message like "Address format is invalid. Please check for any special characters or typos."
While this is a valid issue that needs fixing, we believe the severity rating should be Low rather than High. Even though the error message is technical and could be confusing, it doesn't actually prevent users from completing their tasks - they can still figure out and fix the formatting issue through trial and error. According to our severity guidelines, Low severity is appropriate for cases that cause only minor inconvenience and rarely affect normal operations, which aligns with this scenario.
Furthermore, it is highly unlikely for a "t/" to be in an address.
We'll implement the improved error message in our next update to make the application more user-friendly.
--
Steps to reproduce: Add a person into an empty address book with
person-add m/A0296210X n/John Doe p/98765432 e/johnd@example.com a/John stree t/, block 123, #01-01
where there is a typo in the addressExpected: It should add the person with the typo the in address
Actual: I am given an error message which says tag names should be alphanumerical
As the program mainly uses CLI, typos are common when you type fast, especially in the address where it would be long. Users would be confused about what tag names are as it is not mentioned anywhere in the user guide or developer guide if they make a typo. It could be frustrating for the user as they do not know how to solve the problem and they may stop using the app. Hence i have classified it as a high severity bug.
Perhaps it would be good to mention about tag names in the user guide, or remove it from the code base entirely.
[original: nus-cs2103-AY2425S1/pe-interim#2394] [original labels: severity.High type.FunctionalityBug]