search

pradeep-cod / pe

0 stars 0 forks source link

Never account for human errors for the calories in command #1

Open pradeep-cod opened 6 months ago

pradeep-cod commented 6 months ago

bug1.png

can use trim for the command to take the human error of spaces before or after the slash into account

soc-se-bot commented 6 months ago

Team's Response

No details provided by team.

The 'Original' Bug

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

Never account for human error for spacings for sleep add function

bug2.png

I have entered all keywords it should still take my command into account can use trim input instead

[original: nus-cs2113-AY2324S2/pe-interim#1834] [original labels: severity.Low type.FunctionalityBug]

Their Response to the 'Original' Bug

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

Hi there, thank you for the bug report!

It is imperative to ensure that all keywords are present for the app to function properly. To account for human errors for spacings, we have used the trim input function for all fields except keywords.

Since d whitespace / is not a keyword, the user has used the wrong command, and has been redirected to fix it. The correct command can be seen in the screenshot below.

image.png

Thank you!

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 response Team chose [`response.Rejected`] - [x] I disagree **Reason for disagreement:** Human errors for spaces should still be accounted for even though the keywords entered is correct. Just because i input "d /[DATE]", by right the keywords correct , just that it has extra spaces. Hence, it should still be accounted for