Open nus-se-script opened 1 week ago
Some real life addresses (ranging from geographical to smaller administrative divisions like within buildings/offices) are case sensitive e.g the numbering/indexing of offices. We made the conscious design the decision to reflect this (as opposed to names which are more clear-cut case-insensitive, hence our autoformatter).
Furthermore, we also recategorised the severity and type to adhere to course page more closely.
This can cause occasional inconveniences if the person has hundreds of clients
It is only a valid concern if these hundreds of clients share the same name, phone number and email such that their only distinguishing element is addresses, which is very rare. Hence it is Low.
As a gesture of good faith, we think you might have wanted a feature that warns instances of address that are similar up to casing? In which case, that'd be a nice-to-have feature, and out of scope for the purpose of our project, where we focused on delivering more transaction-related features for financial consultants. We settled on this response because of this reason, and to give the tester some credit.
--
This can cause occasional inconveniences if the person has hundreds of clients. If they choose to add a client whose address has different casing, this duplicate will not be flagged out and they may only realise a while later that they have entered a duplicate.
Screenshot 2024-11-15 at 4.52.30 PM
Screenshot 2024-11-15 at 4.53.28 PM
[original: nus-cs2103-AY2425S1/pe-interim#1418] [original labels: severity.Medium type.FunctionalityBug]