Open nus-se-script opened 11 months ago
This is not a valid issue as It is safe to assume that when a user performs a partial search of let's say a skill, they will search for the first letter, e.g. vfind s/e for engineering.
is not really a valid assumption. For example, if one were to normally perform a ctrl f function and search a web page, you will get all instances of words with the letter e
, and not just the first letter being e
.
You may have users that want to find all volunteers beginning with the letter e
, and you may have users that want to find all volunteers that have the letter e
. Thus we put this as rejected
--
It is safe to assume that when a user performs a partial search of let's say a skill, they will search for the first letter, e.g. vfind s/e for engineering.
However, the app displays all possible skills that have the letter 'e' inside when vfind s/e is executed, skills like 'classmates' and 'friends' show up. It could be frustrating as a user to sieve through these results using vfind.
[original: nus-cs2103-AY2324S1/pe-interim#4815] [original labels: severity.Low type.FeatureFlaw]