Open shawnnlimm opened 5 months ago
This is not a functionality bug.
Team chose [response.Rejected
]
Reason for disagreement: I do not agree that the bug should be rejected since there is clearly a mismatch between what the UG mentioned and the expected output of the feature. Additionally, whitespaces are not considered alphanumeric characters.
NAME
parameter from UG:
If the feature was not intended to accept whitespaces in names, then it is a FunctionalityBug according to the screenshot from the notes below. However, if it is just a typo or information that was missed out by the dev team in the docs, then it is a DocumentationBug.
Description
add
command error message states that the name should only contain alphanumeric characters and spaces, while the UG states that it can only contain alphanumeric characters.Steps to reproduce
add n/hanni pham p/87654321 a/999A t/friend d/tdy 10am-12pm
Expected Behaviour
App should reject the addition of person according to the UG, since a whitespace is included in the name
Actual Behaviour
New person added successfully
Label elaboration
Severity: Low, since it is only a minor inconveniece to the user if any.
BugType: FunctionalityBug, since by following the UG command format, the command above should not be accepted.