Open nus-se-script opened 1 week ago
Users are unlikely to get the wrong idea because maintaining the order of the characters follows the intuitive way of searching. If order of the characters are not maintained, that would overly clutter the results and further confuse the user instead. For example, if users intend to look for the tag CS1231S
and enter 123
it doesn't make sense for tags like CS2103T
to appear. Likewise, users are unlikely to search for Amy
but are actually hoping to get the results Myra
and Mary
. A non-random search order is more intuitive for the user and is unlikely to cause any major issues.
Hence, we decided to reject the bug as it is the expected and correct behaviour from the user's point of view.
--
For the find command, the given example of find an returns armin (characters a and n are present in armin) gives the user the wrong idea that as long as the characters I search for are in the name, the name will be returned. However, the order of the characters matter where find na will not return armin as a must be before n.
[original: nus-cs2103-AY2425S1/pe-interim#482] [original labels: severity.Medium type.DocumentationBug]