search

qinxutan / pe

0 stars 0 forks source link

Command executed despite incorrect command format #4

Open qinxutan opened 2 months ago

qinxutan commented 2 months ago

The edit command is still executed though none of the optional fields were provided:

Expected: Error

A4804B9E-1A47-40C0-8C10-DA5429C96F19.jpeg

Actual: Returns a message that it is edited though nothing was edited as i did not specify the parameters

1C5676AC-052F-4709-B6D6-2336A28559EE.jpeg

Steps to reproduce: Edit command function to throw error when optional fields not specified.

soc-se-bot commented 2 months ago

Team's Response

Hi, this is a duplicate issue, thanks!

The 'Original' Bug

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

Edit command allows no inputs, unlike what the UG says

bug1.png

bug1.png

The edit command allows no imputs to be edited, even though the UG states that there must be at least 1 input. This may lead to confusion as the command returns a success message even though nothing is edited, and may cause confusion to TAs using the app

[original: nus-cs2103-AY2324S2/pe-interim#2476] [original labels: severity.Low type.FeatureFlaw]

Their Response to the 'Original' Bug

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

No details provided by team.

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 severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]