itsme-zeix
commented
1 week ago Team's Response
Thank you for your report, but we have decided to reject this issue as it is working as intended.
The User Guide explicitly states that all fields, including names, are case-insensitive. Consequently, the application treats names as equivalent regardless of capitalization.
This design choice aligns with how names are commonly handled in scenarios such as legal documents and credit cards, where uppercase formatting is standard.
Differentiating names based solely on capitalization is not a typical use case, and ensuring case-insensitivity prevents unnecessary ambiguity.
We appreciate your feedback and encourage you to refer to the User Guide for further clarification.
Duplicate status (if any):
--
Description
The name field in the UI is displayed as caps at all times regardless of the person's name's case sensitivity. This can potentially be an issue when the user needs to differentiate names and chooses to use case sensitivity to differentiate them.
Steps to Reproduce
add n/ JOHN DOE p/ 99007766 e/ mrdoe@ntu.sg a/ com3 j/ doctor i/ 99999 t/ gold r/ got anger issue s/ urgent]add n/ John Doe p/ 99007755 e/ mrdoe@ntu.sg a/ com3 j/ doctor i/ 99999 t/ gold r/ got anger issue s/ urgent] ![Screenshot 2024-11-15 at 4.31.56 PM.png](https://raw.githubusercontent.com/nus-cs2103-AY2425S1/pe/master/files/df9946c9-08f9-47eb-b328-dfcaa7e1d68a.png]Additional Information
Suggested Improvement
An adjustment to display the text as per the user input would fix this issue.
[original: nus-cs2103-AY2425S1/pe-interim#3401] [original labels: severity.Medium type.FeatureFlaw]