gavinsoh / pe

0 stars 0 forks source link

UI does not display the full remark description, when a very long description is added using the "addR" command. #4

Open gavinsoh opened 3 days ago

gavinsoh commented 3 days ago

The command that i entered was: add z/0 r/patient came into the hospital on the 2nd of november 2022 and claimed that he had a very bad headache. as the hospital was very busy that day, he was left unattended. so he went to the toilet by himself. upon entering the toilet, a fellow nurse saw him collapse to the ground and he slipped into a coma. as of now, he still has not woken up yet and there are no emergency contacts related to alex yeoh. doctors are also conflicted on their next course of action.

Upon adding long remarks for the "add remark" command, the remark is truncated and cannot be viewed. This might lead to key information being left out in the remarks section.

I understand that in the Developer Guide, under "Planned Enhancements", the team has stated that "Currently the command box and command result box are relatively small and it will be very hard for users to view the result of the command that they have entered. Hence, to improve on this, we have planned to increase the size of the command result box and also make it more responsive for better readability."

However, if the remark is exceptionally long, the text will still be truncated, regardless of how big the size of the command result box is.

A suggestion is to update the UI such that it allows for a horizontal scroll, so that users can view the whole description of the remark without the risk of missing out any information that might be important to the patient.

Screenshot 2024-11-15 at 16.31.49.png

nus-pe-script commented 2 hours ago

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

Hi! Thank you for the bug report and the observation, and for taking the effort to survey the "Planned Enhancements" portion in the DG. While the portion of the DG you have pointed out could be relevant to this context (point 4 in the image), we believe the next point would be more accurate with regards to this bug (point 5 in the image).

image.png

Due to the feature freeze and the (non-UI) focus placed on the project, we have arranged for this UI functionality to be under planned enhancements.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: [replace this with your reason]