search

glenngnng / pe

0 stars 0 forks source link

Improper use of "ExportCommand" #14

Open glenngnng opened 10 months ago

glenngnng commented 10 months ago

image.png

In the UG, ExportCommand is mentioned. But, as a user that does not know the internals of the app, ExportCommand is unknown and this may cause confusion.

I believe simply using view would be easier to understand :D

nus-pe-bot commented 9 months ago

Team's Response

Hmmm, you are contradicting yourself. Let's assume that the user doesn't know the internals of the app, what makes view easier to understand than export? Both commands require the user to know how the system is supposed to react given a particular command.

Additionally, last I remember in the English dictionary, the word "export" and "view" has a very different meaning. Both commands serve a different functionality and I believe that "view" would not suit the functionality here which in this case, is to transform the data into CSV file format.

Nonetheless, I do get your point and perhaps I can make the UG more user-friendly :D

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Sorry for the confusion! I was a little too caught up in finding bugs.

I did not mean view and actually meant export, but I understand your confusion regarding my mistake in suggestion.

However, I believe that it was merely a small mistake in the suggestion, but the overall intention of pointing out the possibly improper use of "ExportCommand" should still be understood.

I still admit my mistake in using the wrong word "view" for my suggestion.

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [x] I disagree **Reason for disagreement:** As mentioned in the course website, very low severity should only be for cosmetics. But, the use of ExportCommand can hinder the user that does not understand the internals, causing confusion. This should be severity low.