Open Zjinnnn opened 10 months ago
Thank you for your feedback!
In our UG, we stated that if the edits to the JSON file makes the format INVALID. A duplicate field is not considered INVALID format hence, the data will not be deleted.
However, as per CS2103T's severity, a medium severity causes occasional inconvenience. We believe that this will not cause occasional inconvenience as our target audience will not edit the JSON file manually.
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: [replace this with your explanation]
Bug Description:
Making modifications to
friendbook.json
can allow bypass of duplication detection if user was not careful. As mentioned in the UG, advanced users can modify thefriendbook.json
file. However, should an advanced user be careless and accidentally add a space after a name i.e.Tester
and there is another contact namedTester
, duplication detection will not work. File still loads in, but on GUI, it is virtually impossible to differentiate.Bug replication:
friendbook.json
Before:
After: