search

chiageng / pe

0 stars 0 forks source link

Command unable to catch unknown field inserted #15

Open chiageng opened 3 months ago

chiageng commented 3 months ago

Justification : There is a lot command and a lot fields, user will always mistaken some other field exist in certain command, hence i justify as medium

/add :name John Do52325e :phone 9122567 :email john25253doe@email.com :unknown_field ewuhnweugb :address 12Kent Ridge Dr :year 2024 :tag Software Developer :tag Finance

Output : image.png

Expected : Catch unknown field and remind user that this field is not supported by this command. When i remove unknown field, everything work as usual

nus-pe-script commented 2 months ago

Team's Response

We believe users should follow the correct command format which we displayed on the command panel and specified in the user guide. We do not think we can do more than that, like detecting unspecified fields.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: There is a lot of commands to be memorized by user. The application should be more user friendly to guide user to use correct commands.

In most of the cases, user will mistaken of field from other command as one of the field as current command.

For eg: description field exist in add transaction command but not in add employee command. However, user insert description field in add employee causing the command unable to be executed. This flaw will ocassional cause inconvenience to users hence the severity was justify as medium.

This app is catered for fast typist, hence this is an addition to help fast typist to know which part goes wrong, and edit the command promptly. It doesnt make sense for fast typist remembering wrong field, but have to scroll through UG to check command format, when the error messages are also fail to display correct error message which make user even more clueless to understand what is wrong.

We do not think we can do more than that, like detecting unspecified fields. Quote from your explanation. This can be easily done by extracting all fields, and do a checking of each field and make there is no invalid/unknown field for current command. If there is invalid field, you can easily display all invalid fields to user by throwing an error.