nus-pe-bot
commented
4 years ago Team's Response
Hello thank you for your report!
This was actually an intended design which our reason is stated below
- Ease of use for the user. Saves the user time by not having to retype commands. a. User does not have to re-type command if he/she accidentally makes a typo. b. User does not have to re-type command if he/she forgot that there was no parameters needed.
It should be explanatory that we only take the first word as the command word.
Downgraded to very low as it does not affect usage at all.
Can be considered a duplicate of issue #1867 although commands are different.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Reasons given by team was a. User does not have to re-type command if he/she accidentally makes a typo.
- I do not see how this helps typos? If you typo the first word aka the command word, you still need to retype the command. b. User does not have to re-type command if he/she forgot that there was no parameters needed.
- For any command that works through CLI (e.g. command prompt or terminal), you will notice that each command usage must be precise, aka no extra parameters - just the exact command word and its exact number and type of parameters. I think that getting the precise command usage correct is the responsibility of the user, and actually makes it less confusing to the user because they will learn what command format is correct and stick to it.
Thank you for your response, and I'm sorry that I still feel this should be a valid bug!
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: Disagree because it is not some minor bug that does not affect usage. It does affect the very core of your user's actions - the commands through which they interact with the app. If the command usage is not precise, it affects the user because the user will expect that only the exact command usage written in the User Guide will be accepted. It caused much confusion for me when I realised I could add anything after the first command word and it would still work.
Steps to reproduce:
play 1(use the sample 1st deck)flipyes no(or typing any other command starting with "yes" will still get parsed as "yes")A similar problem is encountered with the "no" command - as long as the user input begins with "no", it gets parsed as the "no" command.