Open ruoyann opened 3 years ago
Developers explicitly mention case-insensitive
wherever applicable (for find
and filter
), treating that as the special case.
Team chose [response.NotInScope
]
Reason for disagreement: Case sensitivity matters for add command because users are able to add the same names with different casing. This might confuse the user if they accidentally changed the casing when adding names and a whole new contact is added.
Mentioning of case-insensitivity in certain commands does not explicitly tell the users that other commands are case-sensitive. I still believe that this should be a veryLow documentation bug due to the confusion it can cause readers when they use different casing, which can be considered as expected behaviour (e.g. user typing 'john' as 'John' on separate occasions)
For adding commands