search

Johnchiahk / pe

0 stars 0 forks source link

view function doesn't work #2

Open Johnchiahk opened 1 year ago

Johnchiahk commented 1 year ago

Screenshot (1471).png

When I type "view char John Cena" as stated in the UG, there was no proper error message. In addition, "view mob Skeleton Warrior" and "view item Bow" doesn't work either.

One way this can be rectified if a proper error message such as "view command should be implemented as ...", so that the user understands that he or she may have typed in the wrong command for the view function.

nus-pe-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]

View Char Command Not Working

ViewCharNotWorking.png

Within the User Guide, the command view CLASSIFICATION NAME exists but the command cannot be found in the application.

Users will struggle trying to use the command but can bypass it using edit instead (but very inconvenient)

I assume this is a documentation bug as the command does not exists.

[original: nus-cs2103-AY2223S2/pe-interim#2445] [original labels: severity.Medium type.DocumentationBug]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

View command/feature was actually removed in this pull request. Hence this is not a functionality bug and it is a documentation bug.

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)

Reason for disagreement: [replace this with your explanation]

## :question: Issue type Team chose [`type.DocumentationBug`] Originally [`type.FunctionalityBug`] - [x] I disagree **Reason for disagreement:** From the CS2103T website, The definition of functionality bug is that the behaviour differs from the user guide. The view command was in the user guide and unfortunately, one would expect the view function to work when reading the UG, however, that was not the case. Hence, I believe this is still a functionality bug.
## :question: Issue severity Team chose [`severity.Medium`] Originally [`severity.High`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]