If user accidentally adds an extra character in date for transaction json file, program will infinite loop error messages on next launch. This could potentially be a big issue as if there are thousands of transactions, just one of the dates need to be corrupted for this to happen. It would be very hard for user to find the error manually and program cannot be relaunched until json file is either deleted or that line is mended. I gave this a severity high because program is unusable state if this happen. It might not happen because a user editing json file directly as well. It may have just been a result of file corruption.
Steps to replicate:
create transaction
close application
edit date in json file to simulate corruption
open appication
If user accidentally adds an extra character in date for transaction json file, program will infinite loop error messages on next launch. This could potentially be a big issue as if there are thousands of transactions, just one of the dates need to be corrupted for this to happen. It would be very hard for user to find the error manually and program cannot be relaunched until json file is either deleted or that line is mended. I gave this a severity high because program is unusable state if this happen. It might not happen because a user editing json file directly as well. It may have just been a result of file corruption.
Steps to replicate:
create transaction close application edit date in json file to simulate corruption open appication
[original: nus-cs2113-AY2425S1/pe-interim#28] [original labels: type.FeatureFlaw severity.High]