nus-pe-script
commented
4 months ago Team's Response
Thank you for raising this issue.
This issue is caused by the buggy behaviour of the modify command. This issue alone cannot be fixed without fixing the faulty modify command. This issue has been marked as a duplicate to the issue #1217 which indicated the buggy behaviour of the modify command.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Medication Still Modified With Invalid Input
When modifying the first index on the medication list (1 which is Panadol), into "21" which is invalid. I got thrown with the following error
When looking at the list of medications, using "list -t all" entry number 1 does not change. However when using list -t today. The first entry name becomes modified into "21"
[original: nus-cs2113-AY2324S2/pe-interim#1102] [original labels: type.FunctionalityBug severity.Medium]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Thank you for reporting this. I acknowledge the presence of this bug. This is due to the rollback process of the
Medicationname that did not account for the fact thatDailyMedicationname has been changed, which eventually resulted in this bug occurring.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)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
After data corruption in modifying medication name into invalid input "21", the data can no longer be "modify", "take", ''untaken", and even "deleted".
Modify message did specify that the medicine has been modified, however upon checking the list, it remains unchanged.