taeewonnn / pe

0 stars 0 forks source link

No checks for editing with the same inputs #2

Open taeewonnn opened 7 months ago

taeewonnn commented 7 months ago

Before: Screenshot 2024-04-19 163443.png

Command input: Screenshot 2024-04-19 163457.png

After: Screenshot 2024-04-19 163526.png

We can see that the name of the participant at index 7 is John Doe.

When editting with the same name as shown in command input ss,

There is no check that says it is the same input or rather, it shows that it has been edited. It is not necessary but it may have been better to add a check

nus-pe-script commented 7 months ago

Team's Response

Hi thanks for the suggestion, but it seems like this doesn't affect normal usage. Furthermore, it may not significantly enhance the user experience or the application’s functionality as users typically have a clear intention when they edit data. After making changes, they can easily verify if the data has been updated to their intended input by simply viewing the updated information.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: [replace this with your explanation]


## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]