Fix inverted transaction logic causing payment/request status bug #1678
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
- Extract notification badge logic from NavBar into standalone NotificationBadge component - Add comprehensive Cypress component tests covering edge cases (negative numbers, large numbers, undefined values) - Preserve existing data-test selector for backward compatibility with E2E tests - Use @mui/material to match existing project dependencies - Remove customBadge styling from NavBar component - All 9 component tests passing including Material-UI Badge behavior verification Co-Authored-By: [email protected] <[email protected]>
Extract NotificationBadge component and add comprehensive tests
…58009691 Revert "Extract NotificationBadge component and add comprehensive tests"
This reverts commit 531adfb.
The condition in createTransaction was inverted, causing: - Payment transactions to be marked as 'pending' instead of 'complete' - Request transactions to be marked as 'complete' instead of 'pending' - Balance transfers to incorrectly happen for requests and not for payments Changed line 549 from `if (isRequestTransaction(transaction))` to `if (!isRequestTransaction(transaction))` to properly check if the transaction is a payment (not a request). This fix ensures: - Payments: immediately complete and transfer balances - Requests: remain pending until accepted/rejected All unit tests now passing (44 passed). Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
|
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
createTransaction()functionProblem
The transaction status logic in
backend/database.ts:549was inverted:pendinginstead ofcompletecompleteinstead ofpendingSolution
Changed the condition from
if (isRequestTransaction(transaction))toif (!isRequestTransaction(transaction))to properly check if a transaction is a payment.Test Results
✅ All unit tests passing (44 passed)
should create a payment- now passesshould create a request- now passesFiles Changed
backend/database.ts- Fixed conditional logic (1 line)🤖 Generated with Claude Code