Open matthewgani opened 3 years ago
In our user guide, it is mentioned that users are not recommended to edit the txt files directly as a warning.
Most users would not inject senseless data into the text files unnecessarily and hence, would not face this issue.
Common text file corruption involves corrupted character encoding which will retain the number of entries.This would be accounted for in our program.
Team chose [severity.Low
]
Originally [severity.High
]
Reason for disagreement: Thank you for your response. I disagree with the decrease in severity to low. According to this post https://github.com/nus-cs2113-AY2021S1/forum/issues/117, it is still a valid bug despite you recommending the user not to edit the txt files. According to this post https://github.com/nus-cs2113-AY2021S1/forum/issues/136 which I agree with, a high severity or at least medium is warranted if the user is unable to start up the app the next time and the bug renders the app unusable. I would think adding a few extra lines in a txt file is not an uncommon occurrence when a text file is corrupted and does not seem to be a complicated type of corruption so it could have been dealt with without too much problems.Therefore, I believe it should be a high severity or at least medium.
To replicate: I added the 1 and 11s. The app will not detect the corrupted file and cannot remake it/ allow the user to start the app again.![image.png](https://raw.githubusercontent.com/matthewgani/pe/main/files/fb468855-b8b8-4413-a534-a31b87778df8.png)