no constrain imposed on unreasonable user input

[CShuwen]

the shown input is allowed. which is unreasonable and should have been rejected

[soc-pe-bot]

Team's Response

We are rejecting this because we do not see how this feature will work badly or fail in any way. Our parser will ignore extra colons, as we believe that it might be due to accidental input by the user. For instance, users might first press colon to shift the focus to the command box, and then copy a command from the UG, resulting in two colons. Having this design will give user more convenience as users will not have to retype the whole command due to just a simple mistake.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: As stated in our user guide: every command always starts with a colon (:). your command can also start with multiple colons, which is can be confusing.

---