chore: Remove debug console logs and warnings, and adjust formatting for token address and amount display.

[Yaannko]

Summary of changes:

• Removed console.log("Raw invoices data:", res);
• Removed console.warn("No invoices found.");
• Removed console.warn("Unauthorized access attempt for invoice ${id}");
• Removed console.log(sentInvoices);

Summary by CodeRabbit

• Bug Fixes
  • Improved sent invoices page reliability by ensuring proper data refresh when authentication tokens change.
  • Enhanced display formatting for payment token addresses and transaction amounts in the sent invoices list.
  • Streamlined error handling to provide a cleaner user experience by reducing unnecessary debug messages.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR removes debug logging statements from the SentInvoice component, streamlines error handling by removing the no-invoices warning, adds tokens to the useEffect dependency array, and makes minor formatting adjustments to rendered strings.

Changes

Cohort / File(s)	Summary
Logging & Control Flow Cleanup frontend/src/page/SentInvoice.jsx	Removed console.log statements for raw invoices and sentInvoices; removed console.warn for unauthorized access; simplified no-invoices path to clear state without warning. Added tokens to useEffect dependency array. Minor string formatting adjustments for payment token address and total amount display.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Verify the addition of tokens to the useEffect dependency array is intentional and prevents unintended re-renders or data staleness
• Confirm console logging removal does not eliminate necessary debugging information for production troubleshooting

Possibly related PRs

• Refactor Dashboard, Treasury Account Setup, and Routing #6: Overlaps with logging and UI adjustments to SentInvoice.jsx, including removal of console logs
• Better UX for token selection  #9: Also modifies SentInvoice.jsx with effect dependency changes, including tokens

Suggested reviewers

• adityabhattad2021

Poem

🐰 A cleanup so neat, the logs disappear,
Dependencies sorted, the effect runs clear,
No warnings to clutter, just code crisp and bright,
The invoice component now feels just right! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main changes: removing debug console logs/warnings and adjusting formatting, which aligns with the primary modifications in the changeset.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

frontend/src/page/SentInvoice.jsx (1)

342-342: The dependency addition is correct, but consider memoizing useTokenList's return value.

Adding tokens to the dependency array is necessary since it's used within the effect (via getTokenInfo at line 275). The tokens reference should remain stable across renders because useTokenList's effect only depends on chainId, so excessive re-renders are unlikely.

However, useTokenList in frontend/src/hooks/useTokenList.js returns a new object { tokens, loading, error } on every call. While the destructured tokens array itself is stable when chainId doesn't change, wrapping the return value in useMemo would make referential stability explicit:

export function useTokenList(chainId) {
  const [tokens, setTokens] = useState([]);
  const [loading, setLoading] = useState(false);
  const [error, setError] = useState(null);

  useEffect(() => {
    // ... existing fetch logic
  }, [chainId]);

  return useMemo(() => ({ tokens, loading, error }), [tokens, loading, error]);
}

This ensures that consumers like SentInvoice get a stable object reference when their dependencies haven't changed, improving code clarity.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d2c3742 and aba5fce.

📒 Files selected for processing (1)

• frontend/src/page/SentInvoice.jsx (3 hunks)

🧰 Additional context used

🧬 Code graph analysis (1)

frontend/src/page/SentInvoice.jsx (2)

frontend/src/page/ReceivedInvoice.jsx (2)

• drawerState (96-99)
• fee (78-78)

frontend/src/page/Treasure.jsx (1)

• fee (21-21)

🔇 Additional comments (3)

frontend/src/page/SentInvoice.jsx (3)

176-176: Good cleanup: Debug logging removed.

The removal of console.log("Raw invoices data:", res) is appropriate. Debug logging should not be present in production code.

---

179-179: Good cleanup: Unnecessary warning removed.

The removal of console.warn("No invoices found.") is appropriate. An empty invoice list is a normal state and doesn't warrant a console warning.

---

889-894: LGTM: Formatting improvements for readability.

The multi-line formatting of the token address display (lines 889-894) and total amount calculation (lines 979-984) improves code readability without changing any logic.

Also applies to: 979-984

[Zahnentferner]

These console messages are actually useful. So, I will close this PR without merging.