Open nus-pe-bot opened 2 years ago
It's not super clear from the issue description what the tester's input is, but we believe that it was Ctrl-C
that manually interrupted the app.
We thank the tester for raising this issue and we agree that this behavior is suboptimal. However, we have outlined in our UG that our save and load features are only ensured to work if the app is exited properly from the menu with the exit
command. We have not implemented handling of forced exits, so data is only properly saved if the user follows our UG and exits accordingly. Therefore, we believe this issue is out of scope.
In addition, even though the Ctrl-C
interrupt makes our app show an exception, the app's behavior is essentially still the same as outlined in the UG. As users only need to use the exit
command to ensure that everything works, we believe the severity of this issue is medium, not high. It causes an inconvenience, but it doesn't render the app unusable.
--
[original: nus-cs2113-AY2122S2/pe-interim#554] [original labels: type.FeatureFlaw severity.High]