Feat/budgets - #749
Merged
Merged
Conversation
A pinned widget stored the ObjectBox id of the budget it was pinned to. Budget.toJson omits that id, so restoring a backup reinserts every budget and ObjectBox hands out fresh ones -- "Eating out" comes back as a different number, and that number may already belong to something else. A widget pinned before the restore would then render a different budget's name and progress, confidently, with no sign it had changed subject. The payload now carries Budget.uuid alongside the id, and everything that *persists* a choice keys on it: the iOS AppEntity id (Int -> String, so the sentinel for "any budget that needs attention" is now "automatic" rather than -1) and the Android preference (budgetId_ -> budgetUuid_, where an absent key means auto, so no sentinel value is needed). The id stays in the payload and still backs the deep link -- that URL is built from the payload being rendered, so its id is current by construction. The gap that leaves, a tap landing between a restore and the re-sync, is documented at the call site rather than papered over. payloadVersion goes to 2. Both extensions gate on it exactly, so a v1 payload still sitting in shared storage renders the placeholder until the app next syncs, rather than a budget list nothing can be pinned to. No migration for configurations written under the old keying: these widgets have never shipped, so the only devices holding one are ours. Claude-Session: https://claude.ai/code/session_01E2LauLnkDjeYh4veiEQ9jk
Claude-Session: https://claude.ai/code/session_01E2LauLnkDjeYh4veiEQ9jk
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
1 participant
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.
No description provided.