nus-se-bot
commented
3 years ago Team's Response
The implementation of the find command stems from the aim to maximize the flexibility of the search.
In AB3, the search was mainly to search for a few specific persons. However, in Fine$$e, other search parameters such as range of amounts or range of dates are highly applicable. By allowing the user to specify any data field, it gives the user control over the precision of their search for transactions and optimizes the searches as well.
By omitting this format altogether, the control and flexibility is completely lost. The user would be unable to specify if they want their search terms to be searched in a specific data field. Moreover, specifying a range of dates or amounts will no longer be possible, which makes searching for transactions extremely troublesome and time-consuming. For example, it is far more troublesome to specify multiple dates over a range than to conveniently specify said range with only two additional parameters and two dates.
This is clearly not an optimization of the command at all, as it provides even more inconvience and increases the time taken to search for transactions.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
The current find command has a combination of too many parameter formats which may cause users trouble and cost some amount of time when attempting to do a specific find. Would be better if formats such as 'af/', 'a/', 'd/' were to be omitted altogether, and instead allow users to type find followed by the word they want to find, and then show entries that have that word in any of the fields.