fix: small V1 issues

[rodrigopavezi]

Fixes #29

Changes:

• Fix pdf formatting
• Fix request table columns,
• Fix stats Update "Payment Volume" on landing page to $800+m #29
• Fix gnosis explorer url

Summary by CodeRabbit

• New Features

  • Added a new column for displaying payment references in the request table.
  • Enhanced navigation by linking payee and payer addresses to detailed address pages.

• Improvements

  • Updated the financial figure in the Stats Area from "$700+ Million" to "$800+ Million".
  • Changed the blockchain explorer URL for the XDAI chain to Gnosis Scan.

• Styling

  • Adjusted padding and layout for improved visual presentation in the PDF export template.

[coderabbitai]

Walkthrough

The pull request introduces several updates across multiple components in the codebase. Key changes include the addition of a payment reference column in the request table, updates to the display of payee and payer addresses, a modification to a financial figure in the stats area, and an update to the blockchain explorer URL for the XDAI chain. Additionally, the styling of the PDF export template has been adjusted to improve layout and presentation.

Changes

Files	Change Summary
src/components/request-table.tsx	Added a new column for payment references, modified column headers, and updated address rendering for payees and payers.
src/components/stats-area.tsx	Changed displayed financial figure from "$700+ Million" to "$800+ Million".
src/lib/consts.ts	Updated the URL for CHAINS.XDAI from BlockScout to Gnosis Scan.
src/lib/hooks/use-export-pdf.tsx	Adjusted styling for PDF export template by reducing padding and adding a gap property.

Tip

Announcements

• The review status is no longer posted as a separate comment when there are no actionable or nitpick comments. In such cases, the review status is included in the walkthrough comment.
• We have updated our review workflow to use the Anthropic's Claude family of models. Please share any feedback in the discussion post on our Discord.
• Possibly related PRs: Walkthrough comment now includes a list of potentially related PRs to help you recall past context. Please share any feedback in the discussion post on our Discord.
• Suggested labels: CodeRabbit can now suggest labels by learning from your past PRs in the walkthrough comment. You can also provide custom labeling instructions in the UI or configuration file.
• Possibly related PRs, automatic label suggestions based on past PRs, learnings, and possibly related issues require data opt-in (enabled by default).

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between f4a76f3 and 29210f3.

Files selected for processing (4)

• src/components/request-table.tsx (3 hunks)
• src/components/stats-area.tsx (1 hunks)
• src/lib/consts.ts (1 hunks)
• src/lib/hooks/use-export-pdf.tsx (2 hunks)

Additional comments not posted (9)

src/components/stats-area.tsx (1)

17-17: LGTM!

The change is purely cosmetic, affecting only the visual representation of data within the user interface. The overall structure and logic of the StatsArea function remain unchanged.

src/lib/consts.ts (1)

48-48: LGTM, but verify the impact on the codebase.

The change reflects a shift in the blockchain explorer used for the XDAI chain, transitioning from BlockScout to Gnosis Scan. The alteration does not affect the overall structure or functionality of the CHAIN_SCAN_URLS object.

However, it implies a potential change in the source of data or the preferred tool for users interacting with the XDAI blockchain.

Verify that the change does not break any existing functionality by running the following script:

src/components/request-table.tsx (5)

26-30: LGTM!

The new imports are necessary for the new functionality added in the file. They are correctly specified and do not introduce any issues.

---

48-60: LGTM!

The new column for displaying payment references enhances the table's functionality by providing users with a clear and concise payment reference. The column definition is correctly specified and does not introduce any issues.

---

63-63: LGTM!

The change in the header for the timestamp column reflects a more accurate description of the data being presented, aligning the terminology with common usage in transaction contexts. The change is purely cosmetic and does not introduce any issues.

---

79-88: LGTM!

The changes to the rendering logic for the payee cell enhance the visual presentation by applying a distinct style and improve usability by allowing users to click on the addresses to navigate to more information. The changes are correctly implemented and do not introduce any issues.

---

96-104: LGTM!

The changes to the rendering logic for the payer cell enhance the visual presentation by applying a distinct style and improve usability by allowing users to click on the addresses to navigate to more information. The changes are correctly implemented and do not introduce any issues.

src/lib/hooks/use-export-pdf.tsx (2)

74-74: LGTM!

The reduction in padding from 20px to 5px for the main <div> with ID invoice is approved. This change will create a more compact layout by reducing excess space.

---

86-86: LGTM!

The styling changes to the inner <div> that displays invoice details are approved:

• The reduction in padding from 10px to 5px will reduce excess space.
• The introduction of a gap property with value 2% will improve the alignment of elements.

These changes will enhance the visual presentation of the invoice, potentially leading to a more streamlined and professional appearance in the exported PDF.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.