[Feature]: Improve handling invalid data #11

Closed
opened 2026-05-29 15:50:35 +02:00 by PhoenixPhantom · 0 comments

Currently, when Spellbook reads corrupted or invalid Spellbook data at startup, the data is copied into the invalid.spb file which is located next to the data.spb file where all user data is stored (both files are located under userData/Spellbook for Windows, the app's files directory on Android, ~/Library/'Application Support'/Spellbook or ~/.local/share/Spellbook on Linux).

If this happens, Spellbook should do one of the the following things:

  • Tell the user that the data seems corrupted. Inform them that adding anything to Spellbook in this state will override their data.
  • Allow users to try reload the invalid data (e.g. after they made changes)
Currently, when Spellbook reads corrupted or invalid Spellbook data at startup, the data is copied into the `invalid.spb` file which is located next to the `data.spb` file where all user data is stored (both files are located under `userData/Spellbook` for Windows, the app's files directory on Android, `~/Library/'Application Support'/Spellbook` or `~/.local/share/Spellbook` on Linux). If this happens, Spellbook should do one of the the following things: - Tell the user that the data seems corrupted. Inform them that adding anything to Spellbook in this state will override their data. - Allow users to try reload the invalid data (e.g. after they made changes)
PhoenixPhantom changed title from [Feature]: Add option to load last invalid data to [Feature]: Improve handling invalid data 2026-06-01 15:09:44 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PhoenixPhantom/Spellbook#11
No description provided.