Input command from UserGuide leads to different Result

[bbryant824]

Input command from UserGuide leads to different Result

Description

UserGuide has example input that led to a buyer being added, when i used the exact input as userGuide, the results are different, and indeed, it does not add the buyer at all.

Steps to reproduce

After launching the app , type in command field:
buyer n/Bobby p/91124444 e/bobby123@gmail.com t/friendt/owner

Expected:
Output:
New buyer added: Bobby.
Phone: 91124444; Email: bobby123@gmail.com

Actual
"Tags names should be alphanumeric" as error message

To improve
Change the UG and the function to suit each other.

[nus-pe-bot]

Team's Response

The report appears to be regarding the formatting (lack of spacing) of the User Guide at Use Case #2 of the add buyer command such that it confuses the reader on the exact input to enter into the application.

Above is a screenshot of the same text in the User Guide, and it clearly shows a spacing

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: Thank you for the clarification.

I believe the spacing is the factor causing this problem, and it is wrongly editted on the UserGuide likely due to the formatting or carelessness. From the UserGuide pdf provided for the PE, it is clear that there is no spacing between "t/friend" and "t/owner" as there is no highlighted spacing at the end of first line or start of second line. Thus, the command is technically invalid. Hence, when the command in UG is copy pasted into the app CLI, the problem appeared. This is not a big issue, however, it cause confusion and unclear example in the UserGuide. And from the UserGuide uploaded for PE where i double checked again, the formatting problem is present in the UserGuide.

---