Fix Request pots qa fixes

[Zishan-7]

Bugs https://www.notion.so/peanutprotocol/Request-pots-QA-Session-29c838117579807ab735eee39cb46871

[coderabbitai]

Walkthrough

This PR implements changes across payment flow, user navigation, and UI components. It redirects bank requests to add-money/setup instead of showing minimum-amount errors, adds clickable navigation for Peanut users in contributor cards, refines progress bar visualization for over-goal scenarios, improves token amount input formatting, optimizes request pot payment handling, removes height constraints on contributor lists, and extends utility functions with formatting and Peanut user detection capabilities.

Changes

Cohort / File(s)	Summary
Request Flow & Payment Handling src/components/Common/ActionList.tsx, src/components/Payment/PaymentForm/index.tsx	ActionList now redirects bank requests with small amounts to add-money or setup instead of showing error; PaymentForm adds isRequestPotLink detection to skip setup steps and adjust validation for request pot flows.
Peanut User Features & Navigation src/components/Global/Contributors/ContributorCard.tsx, src/utils/general.utils.ts	ContributorCard introduces clickable navigation to user profiles for Peanut users via useRouter; general.utils adds isPeanutUser field to contributor objects derived from payer account type.
UI Components & Utilities Refinements src/components/Global/ProgressBar/index.tsx, src/components/Global/TokenAmountInput/index.tsx, src/components/TransactionDetails/TransactionDetailsReceipt.tsx	ProgressBar adds over-goal visualization with minimum visual distance between markers; TokenAmountInput formats amounts before onChange propagation; TransactionDetailsReceipt removes max-height constraint on contributors list.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• ProgressBar/index.tsx — Complex over-goal visualization logic with visual distance calculations and conditional formatting requires careful validation of marker positioning and number formatting behavior.
• PaymentForm/index.tsx — Multiple useEffect dependency updates and early-return conditions for request pot flows need verification of control flow and state consistency across payment scenarios.
• TokenAmountInput/index.tsx — Formatting-gated onChange propagation changes behavior subtly; verify that formatting failures don't create unintended state inconsistencies.

Possibly related PRs

• fix(payments): request pot balance validation and navigation issues #1373 — Modifies ActionList.tsx payment-method handling and navigation routing for bank requests with similar redirect-based flow changes.
• fix: semantic request and manteca fulfillment #1278 — Modifies PaymentForm/index.tsx with control flow and useEffect dependency logic for special payment flows (manteca/fulfillUsingManteca), similar pattern to request-pot handling.
• [TASK-15768] feat: Clickable PFPs in txn receipt #1325 — Implements client-side profile navigation using useRouter and conditional styling (like ContributorCard), indicating parallel UI navigation enhancements.

Suggested labels

enhancement

Suggested reviewers

• kushagrasarathe
• jjramirezn
• Hugo0

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "Fix Request pots qa fixes" directly relates to the main changes in the changeset. The modifications across multiple files—including ActionList.tsx, PaymentForm/index.tsx, and utility functions—are primarily focused on addressing request pot functionality and flow issues, which aligns with the title's reference to "Request pots qa fixes." While the phrasing contains some redundancy with "fixes" appearing twice in different forms and could be more specific about the nature of the fixes, it clearly communicates the primary focus area to someone scanning the repository history.
Description Check	✅ Passed	The pull request description provides a link to a Notion document titled "Request-pots-QA-Session," which directly relates to the changeset. The modifications across all files are clearly focused on request pot functionality and addressing QA issues, and the description appropriately references the QA session that likely drove these fixes. Although the description is minimal and provides only a link without additional context, it is related to the changeset and not off-topic or misleading.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/request-pots-qa-fixed

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 07d3b3a and bc9d49d.

📒 Files selected for processing (7)

• src/components/Common/ActionList.tsx (1 hunks)
• src/components/Global/Contributors/ContributorCard.tsx (2 hunks)
• src/components/Global/ProgressBar/index.tsx (2 hunks)
• src/components/Global/TokenAmountInput/index.tsx (1 hunks)
• src/components/Payment/PaymentForm/index.tsx (6 hunks)
• src/components/TransactionDetails/TransactionDetailsReceipt.tsx (1 hunks)
• src/utils/general.utils.ts (3 hunks)

🧰 Additional context used

🧠 Learnings (33)

📓 Common learnings

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#1190
File: src/app/(mobile-ui)/qr-pay/page.tsx:156-176
Timestamp: 2025-09-08T03:13:09.111Z
Learning: In the peanut-ui mobile app, the `/qr-pay` route is only accessed through the DirectSendQR component which always includes the qrCode parameter in the URL when redirecting users to the QR pay page.

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#1190
File: src/app/(mobile-ui)/qr-pay/page.tsx:156-176
Timestamp: 2025-09-08T03:13:09.111Z
Learning: In the peanut-ui mobile app, the `/qr-pay` route is only accessed through the DirectSendQR component which always includes the qrCode parameter in the URL when redirecting users to the QR pay page after scanning MERCADO_PAGO or PIX QR codes.

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1094
File: src/components/AddWithdraw/DynamicBankAccountForm.tsx:279-279
Timestamp: 2025-08-14T08:02:26.705Z
Learning: For hotfixes in the peanut-ui codebase, prefer generic error messages over specific validation error details until the copy can be reviewed with the team, even when the validation functions return detailed error messages.

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#919
File: src/components/Withdraw/views/Initial.withdraw.view.tsx:87-87
Timestamp: 2025-06-18T19:56:55.443Z
Learning: In withdraw flows for Peanut Wallet, the PeanutActionDetailsCard should always display "USDC" as the token symbol because it shows the amount being withdrawn from the Peanut Wallet (which holds USDC), regardless of the destination token/chain selected by the user. The TokenSelector is used for choosing the withdrawal destination, not the source display.

📚 Learning: 2025-08-14T09:20:37.231Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1089
File: src/components/LandingPage/hero.tsx:0-0
Timestamp: 2025-08-14T09:20:37.231Z
Learning: In the hero component at src/components/LandingPage/hero.tsx, the height was intentionally reduced from min-h-[100vh] to h-[90vh] to improve scrollability discoverability - so users can see there's more content below to scroll. The overflow-y-hidden is acceptable when other elements are adjusted to prevent clipping.

Applied to files:

• src/components/TransactionDetails/TransactionDetailsReceipt.tsx

📚 Learning: 2025-10-24T13:44:39.473Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1332
File: src/components/Global/TokenAmountInput/index.tsx:141-150
Timestamp: 2025-10-24T13:44:39.473Z
Learning: In the `TokenAmountInput` component (`src/components/Global/TokenAmountInput/index.tsx`), the slider feature (controlled by `showSlider` prop) is only shown for USD input mode. When the slider is used with `maxAmount`, the `selectedAmount` is computed in USD and `isInputUsd` is always `true`, so the conversion in `onChange` handles it correctly.

Applied to files:

• src/components/Global/TokenAmountInput/index.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2024-10-29T12:19:41.968Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#495
File: src/components/Global/TokenAmountInput/index.tsx:23-30
Timestamp: 2024-10-29T12:19:41.968Z
Learning: In the `TokenAmountInput` component (`src/components/Global/TokenAmountInput/index.tsx`), when the 'Max' button is clicked, we intentionally set the input denomination to 'TOKEN' because we are setting the value as token.

Applied to files:

• src/components/Global/TokenAmountInput/index.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2024-10-29T12:20:47.207Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#495
File: src/components/Create/Link/Input.view.tsx:244-248
Timestamp: 2024-10-29T12:20:47.207Z
Learning: In the `TokenAmountInput` component within `src/components/Global/TokenAmountInput/index.tsx`, when `balance` is undefined, the `maxValue` prop should be set to an empty string `''`.

Applied to files:

• src/components/Global/TokenAmountInput/index.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2025-08-22T07:25:59.304Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1104
File: src/components/Payment/PaymentForm/index.tsx:596-600
Timestamp: 2025-08-22T07:25:59.304Z
Learning: The `TokenAmountInput` component in `src/components/Global/TokenAmountInput/` always returns decimal strings (e.g., "1,234.56"), not base units. When passing these values to external APIs like Daimo's `toUnits` prop, simply stripping commas with `.replace(/,/g, '')` is sufficient.

Applied to files:

• src/components/Global/TokenAmountInput/index.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2024-10-08T20:13:42.967Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#413
File: src/context/tokenSelector.context.tsx:118-123
Timestamp: 2024-10-08T20:13:42.967Z
Learning: In the `TokenContextProvider` component within `src/context/tokenSelector.context.tsx`, in the TypeScript React application, when data changes and before calling `fetchAndSetTokenPrice`, it is necessary to reset `selectedTokenData`, `selectedTokenPrice`, `selectedTokenDecimals`, and `inputDenomination` to discard stale data.

Applied to files:

• src/components/Global/TokenAmountInput/index.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2024-10-07T15:25:45.170Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#422
File: src/components/Request/Pay/Views/Initial.view.tsx:76-78
Timestamp: 2024-10-07T15:25:45.170Z
Learning: In `src/components/Request/Pay/Views/Initial.view.tsx`, both `txFee` and `utils.formatTokenAmount(...)` return strings, ensuring that `calculatedFee` consistently returns a string without the need for additional type conversion.

Applied to files:

• src/components/Global/TokenAmountInput/index.tsx
• src/components/Global/ProgressBar/index.tsx
• src/components/Common/ActionList.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2024-10-07T15:28:25.280Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#422
File: src/components/Request/Pay/Views/Initial.view.tsx:76-78
Timestamp: 2024-10-07T15:28:25.280Z
Learning: In `src/components/Request/Pay/Views/Initial.view.tsx`, both `txFee` and `utils.formatTokenAmount(estimatedGasCost, 3)` return strings, ensuring consistent return types for `calculatedFee`.

Applied to files:

• src/components/Global/TokenAmountInput/index.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2025-10-29T11:27:59.248Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1368
File: src/components/Common/ActionList.tsx:109-111
Timestamp: 2025-10-29T11:27:59.248Z
Learning: In `src/components/Common/ActionList.tsx`, the `balance` from `useWallet()` hook is always in USDC (as a formatted string), making it directly comparable to USD amounts without conversion. The comparison `Number(balance) >= amountInUsd` is intentional and correct.

Applied to files:

• src/components/Global/TokenAmountInput/index.tsx
• src/components/Common/ActionList.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2024-10-11T01:14:15.489Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#424
File: src/components/Global/TokenSelector/TokenSelector.tsx:197-211
Timestamp: 2024-10-11T01:14:15.489Z
Learning: In `src/components/Global/TokenSelector/TokenSelector.tsx`, when the calculation within functions like `byChainAndText` is not computationally expensive, it's acceptable to avoid using `useCallback` for memoization.

Applied to files:

• src/components/Global/TokenAmountInput/index.tsx

📚 Learning: 2024-12-11T10:13:22.806Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#564
File: src/components/Request/Pay/Views/Initial.view.tsx:430-430
Timestamp: 2024-12-11T10:13:22.806Z
Learning: In the React TypeScript file `src/components/Request/Pay/Views/Initial.view.tsx`, when reviewing the `InitialView` component, do not flag potential issues with using non-null assertion `!` on the `slippagePercentage` variable, as handling undefined values in this context is considered out of scope.

Applied to files:

• src/components/Global/TokenAmountInput/index.tsx
• src/components/Global/ProgressBar/index.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2025-05-19T19:40:43.138Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#868
File: src/components/Payment/PaymentForm/index.tsx:284-293
Timestamp: 2025-05-19T19:40:43.138Z
Learning: When converting between USD and token amounts, always check if the token price (divisor) is valid and non-zero before performing the division to prevent Infinity, NaN, or errors. Implementing validation like `if (!tokenPrice || isNaN(tokenPrice) || tokenPrice === 0)` before division operations is crucial for handling cases where price data might be unavailable.

Applied to files:

• src/components/Global/TokenAmountInput/index.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2024-10-29T14:44:08.745Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#495
File: src/components/Cashout/Components/Initial.view.tsx:194-198
Timestamp: 2024-10-29T14:44:08.745Z
Learning: Using a fixed 6 decimal places for `floorFixed` is acceptable for token amounts in this codebase, even if tokens have varying decimal places.

Applied to files:

• src/utils/general.utils.ts

📚 Learning: 2025-09-18T09:30:42.901Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1230
File: src/app/(mobile-ui)/withdraw/page.tsx:92-97
Timestamp: 2025-09-18T09:30:42.901Z
Learning: In src/app/(mobile-ui)/withdraw/page.tsx, the useEffect that calls setShowAllWithdrawMethods(true) when amountFromContext exists is intentionally designed to run only on component mount (empty dependency array), not when amountFromContext changes. This is the correct behavior for the withdraw flow where showing all methods should only happen on initial load when an amount is already present.

Applied to files:

• src/components/Common/ActionList.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2025-08-26T15:25:53.328Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1132
File: src/app/[...recipient]/client.tsx:394-397
Timestamp: 2025-08-26T15:25:53.328Z
Learning: In `src/components/Common/ActionListDaimoPayButton.tsx`, the `handleCompleteDaimoPayment` function should not display error messages to users when DB update fails because the Daimo payment itself has succeeded - showing errors would be confusing since the payment was successful.

Applied to files:

• src/components/Common/ActionList.tsx

📚 Learning: 2024-10-25T11:33:46.776Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#484
File: src/components/Cashout/Components/Initial.view.tsx:273-274
Timestamp: 2024-10-25T11:33:46.776Z
Learning: In the `InitialCashoutView` component (`src/components/Cashout/Components/Initial.view.tsx`), linked bank accounts should not generate error states, and the `ValidatedInput` component will clear any error messages if needed. Therefore, it's unnecessary to manually clear the error state when selecting or clearing linked bank accounts.

Applied to files:

• src/components/Common/ActionList.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2025-05-22T15:38:48.586Z

Learnt from: kushagrasarathe
PR: peanutprotocol/peanut-ui#869
File: src/app/(mobile-ui)/withdraw/page.tsx:82-88
Timestamp: 2025-05-22T15:38:48.586Z
Learning: The country-specific withdrawal route exists at src/app/(mobile-ui)/withdraw/[...country]/page.tsx and renders the AddWithdrawCountriesList component with flow="withdraw".

Applied to files:

• src/components/Common/ActionList.tsx

📚 Learning: 2024-10-08T20:13:42.967Z

Learnt from: Hugo0
PR: peanutprotocol/peanut-ui#420
File: src/components/Offramp/Offramp.consts.ts:27-28
Timestamp: 2024-10-08T20:13:42.967Z
Learning: In `src/components/Offramp/Offramp.consts.ts`, the `MIN_CASHOUT_LIMIT` is set to $10 because smaller amounts are impractical due to approximately $1 fee per cashout.

Applied to files:

• src/components/Common/ActionList.tsx

📚 Learning: 2025-10-02T15:23:01.513Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1266
File: src/app/(mobile-ui)/withdraw/[country]/bank/page.tsx:46-57
Timestamp: 2025-10-02T15:23:01.513Z
Learning: In the withdraw flow at src/app/(mobile-ui)/withdraw/[country]/bank/page.tsx, the points calculation query intentionally uses crypto.randomUUID() in the queryKey dependency array to bypass React Query caching, ensuring fresh points estimates on every render. This is the intended behavior.

Applied to files:

• src/components/Common/ActionList.tsx

📚 Learning: 2025-08-14T14:42:54.411Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1094
File: src/utils/withdraw.utils.ts:181-191
Timestamp: 2025-08-14T14:42:54.411Z
Learning: The countryCodeMap in src/components/AddMoney/consts/index.ts uses uppercase 3-letter country codes as keys (like 'AUT', 'BEL', 'CZE') that map to 2-letter country codes, requiring input normalization to uppercase for proper lookups.

Applied to files:

• src/components/Common/ActionList.tsx

📚 Learning: 2024-10-23T09:38:27.670Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#469
File: src/app/request/pay/page.tsx:32-64
Timestamp: 2024-10-23T09:38:27.670Z
Learning: In `src/app/request/pay/page.tsx`, if `linkRes` is not OK in the `generateMetadata` function, the desired behavior is to use the standard title and preview image without throwing an error.

Applied to files:

• src/components/Common/ActionList.tsx

📚 Learning: 2024-10-08T20:13:42.967Z

Learnt from: Hugo0
PR: peanutprotocol/peanut-ui#422
File: src/components/Request/Pay/Pay.tsx:113-123
Timestamp: 2024-10-08T20:13:42.967Z
Learning: In the `PayRequestLink` component (`src/components/Request/Pay/Pay.tsx`), when resolving ENS names, handle errors by displaying an appropriate error message to the user if the ENS cannot be resolved.

Applied to files:

• src/components/Common/ActionList.tsx
• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2024-10-07T15:50:29.173Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#422
File: src/components/Request/Pay/Pay.consts.ts:34-34
Timestamp: 2024-10-07T15:50:29.173Z
Learning: In `src/components/Request/Pay` components, the `tokenPrice` property in the `IPayScreenProps` interface is only relevant to these views. Other components using `IPayScreenProps` do not need to handle `tokenPriceData` when it's updated in these components.

Applied to files:

• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2024-12-02T17:19:18.532Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#551
File: src/components/Request/Create/Views/Initial.view.tsx:151-156
Timestamp: 2024-12-02T17:19:18.532Z
Learning: In the `InitialView` component at `src/components/Request/Create/Views/Initial.view.tsx`, when setting the default chain and token in the `useEffect` triggered by `isPeanutWallet`, it's acceptable to omit the setters from the dependency array and not include additional error handling for invalid defaults.

Applied to files:

• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2024-10-08T20:13:42.967Z

Learnt from: Hugo0
PR: peanutprotocol/peanut-ui#413
File: src/components/Request/Pay/Views/Initial.view.tsx:71-72
Timestamp: 2024-10-08T20:13:42.967Z
Learning: In `src/components/Request/Pay/Views/Initial.view.tsx`, it's acceptable to use the `!` operator in TypeScript to assert that `selectedTokenData` is not `null` or `undefined`, and potential runtime errors from accessing its properties without checks can be disregarded.

Applied to files:

• src/components/Payment/PaymentForm/index.tsx
• src/components/Global/Contributors/ContributorCard.tsx

📚 Learning: 2025-08-22T07:28:32.281Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1104
File: src/components/Payment/PaymentForm/index.tsx:522-545
Timestamp: 2025-08-22T07:28:32.281Z
Learning: In `src/components/Payment/PaymentForm/index.tsx`, the `handleCompleteDaimoPayment` function is only for updating payment status in the backend after a successful Daimo payment. Payment success/failure is handled by Daimo itself, so try/catch error handling and error display are not needed for backend sync failures - users shouldn't see errors if payment succeeded but database update failed.

Applied to files:

• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2024-10-07T13:42:00.443Z

Learnt from: Hugo0
PR: peanutprotocol/peanut-ui#422
File: src/components/Request/Pay/Pay.tsx:103-111
Timestamp: 2024-10-07T13:42:00.443Z
Learning: When the token price cannot be fetched in `src/components/Request/Pay/Pay.tsx` within the `PayRequestLink` component, set `tokenPriceData.price` to 0 to ensure the UI remains functional. Since Squid uses their own price engine for x-chain fulfillment transactions, this approach will not affect the transaction computation.

Applied to files:

• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2025-01-16T13:14:40.363Z

Learnt from: jjramirezn
PR: peanutprotocol/peanut-ui#631
File: src/components/Create/Create.tsx:108-112
Timestamp: 2025-01-16T13:14:40.363Z
Learning: In the Peanut UI codebase, the `resetTokenContextProvider` function from `tokenSelectorContext` is a stable function reference that doesn't change, so it doesn't need to be included in useEffect dependencies.

Applied to files:

• src/components/Payment/PaymentForm/index.tsx

📚 Learning: 2025-07-24T13:26:10.290Z

Learnt from: Hugo0
PR: peanutprotocol/peanut-ui#1014
File: src/components/Claim/Link/Initial.view.tsx:413-413
Timestamp: 2025-07-24T13:26:10.290Z
Learning: In the peanut-ui repository, the change from `${SQUID_API_URL}/route` to `${SQUID_API_URL}/v2/route` in src/components/Claim/Link/Initial.view.tsx was a typo fix, not an API migration, as the codebase was already using Squid API v2.

Applied to files:

• src/components/Global/Contributors/ContributorCard.tsx

📚 Learning: 2025-09-05T07:31:11.396Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1185
File: src/components/Claim/useClaimLink.tsx:14-0
Timestamp: 2025-09-05T07:31:11.396Z
Learning: In the peanut-ui codebase, `window.history.replaceState` is preferred over `router.replace` when immediate/synchronous URL parameter updates are required, as `router.replace` is asynchronous and doesn't guarantee instant URL changes that subsequent code can rely on. This pattern is used consistently across usePaymentInitiator.ts, Confirm.payment.view.tsx, and useClaimLink.tsx.

Applied to files:

• src/components/Global/Contributors/ContributorCard.tsx

📚 Learning: 2025-05-13T10:05:24.057Z

Learnt from: kushagrasarathe
PR: peanutprotocol/peanut-ui#845
File: src/components/Request/link/views/Create.request.link.view.tsx:81-81
Timestamp: 2025-05-13T10:05:24.057Z
Learning: In the peanut-ui project, pages that handle request flows (like Create.request.link.view.tsx) are only accessible to logged-in users who will always have a username, making null checks for user?.user.username unnecessary in these contexts.

Applied to files:

• src/components/Global/Contributors/ContributorCard.tsx

📚 Learning: 2025-09-05T07:31:11.396Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1185
File: src/components/Claim/useClaimLink.tsx:14-0
Timestamp: 2025-09-05T07:31:11.396Z
Learning: In the peanut-ui codebase, `window.history.replaceState` is used instead of `router.replace` in URL manipulation functions when immediate/synchronous URL updates are required for subsequent actions to read the updated URL parameters.

Applied to files:

• src/components/Global/Contributors/ContributorCard.tsx

🧬 Code graph analysis (4)

src/components/Global/TokenAmountInput/index.tsx (1)

src/utils/general.utils.ts (1)

• formatTokenAmount (335-374)

src/components/Global/ProgressBar/index.tsx (1)

src/utils/general.utils.ts (2)

• formatCurrency (270-272)
• formatExtendedNumber (658-706)

src/components/Payment/PaymentForm/index.tsx (2)

src/utils/general.utils.ts (1)

• formatAmount (282-322)

src/redux/slices/send-flow-slice.ts (1)

• setUsdValue (53-55)

src/components/Global/Contributors/ContributorCard.tsx (2)

src/components/Global/Card/index.tsx (1)

• CardPosition (4-4)

src/utils/color.utils.ts (1)

• getColorForUsername (51-69)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Deploy-Preview

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
peanut-wallet	Ready	Preview	Comment	Oct 30, 2025 5:41pm

[Hugo0]

@coderabbitai review in depth

[coderabbitai]

@Hugo0: I'll perform an in-depth review of all the changes in this PR.

---

🧠 Learnings used

Learnt from: Hugo0
PR: peanutprotocol/peanut-ui#823
File: src/context/kernelClient.context.tsx:79-86
Timestamp: 2025-04-29T19:36:38.121Z
Learning: When Hugo0 asks to "resolve coderabbit comments", they want to acknowledge the comment without necessarily implementing the suggested changes, as the current implementation might be intentional for their specific use case.

---

Learnt from: Hugo0
PR: peanutprotocol/peanut-ui#594
File: src/components/Request/Pay/Views/Initial.view.tsx:188-213
Timestamp: 2024-12-31T15:08:15.640Z
Learning: Always resolve coderabbit comments when reviewing code, since they can contain useful suggestions.

---

Learnt from: Hugo0
PR: peanutprotocol/peanut-ui#852
File: src/hooks/useTransactionHistory.ts:177-239
Timestamp: 2025-05-14T21:16:06.369Z
Learning: When reviewing code, pay attention to and resolve CodeRabbit comments as they can contain useful refactoring suggestions and insights.

---

Learnt from: Hugo0
PR: peanutprotocol/peanut-ui#942
File: src/components/AddMoney/consts/index.ts:2151-2162
Timestamp: 2025-06-30T10:44:08.048Z
Learning: Hugo0 often agrees with refactoring suggestions but defers implementation due to time constraints, preferring to track improvements as follow-up issues when they're part of larger architectural changes.

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.