nus-se-script
commented
1 year ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
UG Example for linkcontact cut off or missing
Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
The linkcontact example part for the UG is either cut off or missing and it does not display the entire text.
[original: nus-cs2103-AY2223S2/pe-interim#2218] [original labels: severity.VeryLow type.DocumentationBug]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Indeed that the full text message of the output is cut off, however the intentions of putting the output is to show the users that the user should be looking out for the output that indicates that the event is "Succesfully linked!..." and the rest of the output is not relevant as it is subjective to the events that the users have input already in their event book.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue response Team chose [`response.NotInScope`] - [x] I disagree **Reason for disagreement:** The output should reflect what is expected to be seen, for e.g linkcontact section on sample output should show how exactly the output looks like and also which specific new contact linked so that the user knows what it should look like. Either case, it is indeed a low severity cosmetic bug and there is no reason to cut it off oddly like you have done so.
Last line is cut-off
**EDIT: The same issue is seen throughout the document for longer outputs e.g linkcontact, unmark sections