Repository navigation
Track each person’s half of shared bills independently - #20
Merged
Merged
Conversation
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.
Shared bills now show a named half-payment confirmation for each participant. The active profile can confirm or undo only its own half in the UI; both profiles see the separate results. Confirmations are month-specific, and existing bills do not gain inferred confirmations. My half pending/paid filters help find unfinished payments.
Provider payment remains a separate Bill: Paid action. The configured bill payer is restored as the common default across profiles, while explicit saved payers and paid history remain unchanged. For provider-paid bills, confirming the non-payer’s half records reimbursement and clears that bill from the amount owed; undo restores it. Budget amounts and provider-payment status are unaffected by personal confirmations.
Validation: npm run check passed (52 tests). Browser checks covered independent profile buttons, common payer default, reimbursement balance updates, share filters and no desktop overflow.