nus-se-bot
commented
2 months ago Team's Response
Most email addresses follow a common format, and that format is acceptable within the bounds of our input validation (and also stated in our error messages).
Hence, we did not see a need to explicitly mention this constraint as it would already fit what most end users expect.
However, for the sake of consistency, we accept this as a very low severity, minor documentation bug.
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Low]
- [x] I disagree
Reason for disagreement: No constrains stated in the UG might not affected normal operations of produce but it can cause inconvience in rare situations such as the users is not familiar with email address and forget the format of email. This fits the description of severity.low
As shown in the exception messages of add command, every fields have they own constrains, however, in the new user tutorial or the feature section, the constrains of some field are not stated. For exampple, the email field in add command: the exception message:
the new user tutorial:
the feature sections:
the constrains of email field is also not included in the edit command.