chore(bridge): drop KYC-response console.logs#649
Merged
Conversation
Removes two `console.log("BRIDGE INITIATE KYC RESPONSE: ", res)` statements in
the Bridge KYC-initiation flow (AccountType.tsx, TopupCashout.tsx). Logging the
KYC response writes sensitive identity data to the console; it serves no
purpose in production. `res` is still used for error handling, so behavior is
unchanged.
Surfaced during review of #621. The transaction-details TODO stub on the
cashout success screen is intentionally left as-is.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Summary
Removes two
console.log("BRIDGE INITIATE KYC RESPONSE: ", res)statements in the Bridge KYC-initiation flow:app/screens/account-upgrade-flow/AccountType.tsxapp/screens/topup-cashout-flow/TopupCashout.tsxLogging the raw KYC response writes sensitive identity data to the console and serves no production purpose.
resis still used for error handling immediately after, so behavior is unchanged.Scope
payment-success-screen.tsx) is intentionally left as-is per the review decision.Note on sequencing
This targets
feat/fygaro, so it needs to land here before #621 (feat/fygaro → main) is merged for the cleanup to be included. Two-line deletion; no behavior change.🤖 Generated with Claude Code