Preserve incompatible and drawing-only board data - #103
Merged
Conversation
This was referenced Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Root cause
Decode failures fell back to a text card that later autosave/navigation/quit paths could write over the original bytes. Blankness was also derived only from the lossy text mirror, so unnamed drawing-only boards could be pruned.
Validation
swift test --filter BoardPersistenceTests— 15 passed./script/check— release build plus 184 tests passed./script/verify— release bundle identity/update/icon verification passedgit diff --cached --check— passedThe unrelated local
opencode.jsondeletion is not included.Closes #102
Closes #97