-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Fix inverted transaction type logic in createTransaction #1680
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
kevintang513
wants to merge
14
commits into
cypress-io:develop
from
kevintang513:fix/transaction-type-logic
Closed
Fix inverted transaction type logic in createTransaction #1680
kevintang513
wants to merge
14
commits into
cypress-io:develop
from
kevintang513:fix/transaction-type-logic
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.
Simplified allowed-tools from pattern-based permissions to general Bash access to resolve permission issues when running the command. Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
The condition was checking for request transactions but executing payment logic (immediate balance transfer and completion), and vice versa. This caused payments to only send notifications and requests to immediately complete, which is the opposite of intended behavior. 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
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()that was causing payments to behave as requests and vice versaif (isRequestTransaction(transaction))toif (!isRequestTransaction(transaction))Changes
File:
backend/database.ts:549isRequestTransaction()condition to correctly execute payment logic for paymentsImpact
This fixes a critical bug where:
The logic now correctly implements:
Test Plan
yarn test:unittransactions.test.tstests "should create a payment" and "should create a request" now pass🤖 Generated with Claude Code