search

shoibloya / pe

0 stars 0 forks source link

The help message is not well formated #9

Open shoibloya opened 2 years ago

shoibloya commented 2 years ago

Help message is not well formatted making it very hard to read. Furthermore, the change of modes is not specified in the command table.

nus-se-script commented 2 years ago

Team's Response

Our team think that information given in the help command is already the bare minimum and adding more space will require users to scroll more as the command table is very long due to the complexity of our program. Hence, although it might be easier to read by adding empty lines in between, we feel that in our case, it is better not to add empty lines. Also, we feel that change of modes is not really a command as it does not do any "real work" in MediVault and thus it was written at the top of the command table. Hence, rejected.

Similar issue to 1843.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Help command is not very userfriendly

image.png

The notes given at the start of the help command are a little cluttered. Perhaps separating lines with an additional empty line in between to make it easier to read for users.

[original: nus-cs2113-AY2122S1/pe-interim#1816] [original labels: type.FeatureFlaw severity.VeryLow]

Their Response to the 'Original' Bug

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

Our team think that information given in the help command is already the bare minimum and adding more space will require users to scroll more as the command table is very long due to the complexity of our program. Hence, although it might be easier to read by adding empty lines in between, we feel that in our case, it is better not to add empty lines. Hence, rejected.

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 reason]

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: [replace this with your reason]

:question: Issue type

Team chose [type.FeatureFlaw] Originally [type.DocumentationBug]

Reason for disagreement: [replace this with your reason]

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Low]

Reason for disagreement: [replace this with your reason]