jundatan
commented
1 year ago Team's Response
Our team disagree that the OR function of find is counterintuitive. It can be useful for some people like finding all clients that consists any of the keywords for each field. One example is that Tom wants to find the clients who are Tom but he also wishes to find clients who are 50kg. This allows him to see the all the clients that matches the description easily so that he does not need to do find twice.
Hence, it may be counterintuitive for the owner of this bug report but it may be useful for other users.
Duplicate status (if any):
--
When finding by multiple prefixes, users would tend to prefer to narrow down their search. For e.g., when I were to enter the command "find n/char p/9" I would possibly hope to only return the index 3 "Charlotte Oliveiro", whom matches "char" that I entered, and phone number that starts with 9.
However, the OR function results in it to return all 9 clients. This counter-acts the function of "find", and the purpose of allowing a user to narrow down a client by multiple prefix.
[original: nus-cs2103-AY2223S2/pe-interim#504] [original labels: severity.Low type.FeatureFlaw]