Name constraints gap

[nus-se-script]

States "S/O" or "D/O" is accepted,

• no example of proper use - important as it is an exception to the rules
• case sensitivity not specified

---

_{[original: nus-cs2103-AY2425S1/pe-interim#2158] [original labels: severity.Low type.DocumentationBug]}

[yu-sutong]

Team's Response

It is stated that not every nitty-gritty details need to be included. For users putting in "S/O" or "D/O", they are expected to know how "S/O" and "D/O" roughly work in names, or at least be able to refer to the customer's name when inputting the name. Choosing to put an example for all these specific types of names (e.g. S/O, -, ') may end up resulting in a lot of examples due to the large range of types of names. Hence, no example was included for such specific cases.

Users can interpret from our UG how S/O and D/O can be used and should be in upper case as per how "S/O" and "D/O" normally operates in real-world scenario, which is naturally capitalized. (also, as stated earlier, they are expected to know how "S/O" and "D/O" roughly works)

Hence, this response is rejected.

Duplicate status (if any):

--