Open chishanw opened 4 years ago
Thank you for your report!
The UG also stated that there should only be 1 colon used. Hence, the user should also be reminded of that fact. However we accept that the exception message should be more specific.
Since the UG has already mentioned this point, we will downgrade this to severity low as it only causes a minor inconvenience (of having to check the UG)
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: [replace this with your explanation]
UG states that there can only be one colon in the edit command, and no colon in the card face values. e.g.
edit front:back
User input:
edit front:back :
Expected: Error message telling me there should not be a colon in the face values. E.g. the error message the user receives when they type
edit front::back
, as seen here:Actual: Error message telling user that the command is invalid. This is not specific enough, because the error message for colons in the card face values does exist already, but was not used for this particular edge case where the extra colon is at the back of the command.