soc-pe-bot
commented
1 year ago Team's Response
Thanks for the suggestion! We have explained this design decision in detail in the DG under the Design Considerations section of Implementation of the Find Command Feature as seen below:
For the intended usage of our project, we wish to avoid clutter is list display and thereby in light of user ease and convenience, have decided to structure the find command this way. The word-by-word matching has also been addressed in the UG to prevent any confusion in this regard, as seen below:
Therefore this, was indeed the intended behavior of the app. We have marked this as NotInScope instead of Rejected as we think that though the find command in DevEnable as per v1.4 works as expected (design decision explained above), we may implement another command in the future for partial searches exclusively. However, that does not fall under the scope of our current work.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
As shown, does not find projects when I type "Pro".
But when "Project" was keyed in
If it was intended, I might find it alittle hard to remember the full name of the project (let's say it some not so common name like LumiNUS, which has acronyms that I might not remember it's spelling all the time).