Can be a big issue because all user transaction data will be irretrievably lost if json is corrupted. It might not even be a result of user editing hence corrupt. It might have just been a system caused corruption. Perhaps instead of purging all transactions, can just delete that line instead? So it is not so damaging to the user.
Steps to replicate:
add as many transactions
close app
edit transactions json to simulate corrupt data
reopen app
Can be a big issue because all user transaction data will be irretrievably lost if json is corrupted. It might not even be a result of user editing hence corrupt. It might have just been a system caused corruption. Perhaps instead of purging all transactions, can just delete that line instead? So it is not so damaging to the user.
Steps to replicate:
add as many transactions close app edit transactions json to simulate corrupt data reopen app
[original: nus-cs2113-AY2425S1/pe-interim#29] [original labels: type.FeatureFlaw severity.Low]