nus-pe-script
commented
1 year ago Team's Response
The commands "editp/addp" and "findp" are very different from each other, so it's unlikely that users will mix them up.
The behavior of command is as intended, as there's no need to hit enter. This feature is meant to improve the user experience when searching for specific tasks.
Imagine if you have a big list of data to search through, it's unlikely that you can memorize the full names of all the data, and you may only remember partial names. By providing a responsive search feature, users can perform fuzzy searches to find the data more easily.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Agree with your explanation! The responsive search feature works great, however, I think perhaps the issue here is the word choice in the UG.
This seems like it could be a Documentation bug instead. Your Tip states "Upon entering the findp command, ..." which can be misleading since "entering" could mean hitting the enter key (and assumed so since all the other commands work by hitting the enter key). I think a better way to reword it would be "Upon typing findp into the command box, ...".
UG states that "Upon entering the findp command,....", however, this takes effect before I hit enter. (could be a phrasing issue or functionality issue)
Also, not sure if this is the best way to implement the command as well since users could've wanted to type editp/addp and accidentally type findp, and before hitting enter, the display has already changed and they might need to relocate the person's index so that they can perform editp/addp.