A failed initial read of the database does not prevent saving #123

New Issue

wojtek · 2024-02-08T22:57:36+01:00

wojtek commented

2024-02-08 22:57:36 +01:00

If the initial database read fails, there is very little preventing the user from saving the empty state from being saved back to disk. Pressing q will trigger the save, even if the quit won't happen on the error screen. Preventing saving on error screens is also not enough. The user can dismiss the error and then the data may save.

There should be some mechanism to prevent the user from saving the invalid data. Perhaps a new "Catastrophic Error" state which has only one outgoing action - to exit without saving?

If the initial database read fails, there is very little preventing the user from saving the empty state from being saved back to disk. Pressing `q` will trigger the save, even if the quit won't happen on the error screen. Preventing saving on error screens is also not enough. The user can dismiss the error and then the data may save. There should be some mechanism to prevent the user from saving the invalid data. Perhaps a new "Catastrophic Error" state which has only one outgoing action - to exit without saving?

wojtek added the

bug

label 2024-02-08 22:57:55 +01:00

wojtek added this to the v0.2.0 milestone 2024-02-08 22:57:58 +01:00

wojtek added reference 123---a-failed-initial-read-of-the-database-does-not-prevent-saving

2024-02-09 19:24:56 +01:00

wojtek referenced a pull request that will close this issue

2024-02-09 19:25:10 +01:00

Add critical error state #124

wojtek closed this issue

2024-02-09 20:07:48 +01:00

wojtek referenced this issue from a commit