Skip to content

[Dashboard] Fix: Routes page pagination beyond 1, add og image #7136

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

Merged
merged 1 commit into from
May 23, 2025

Conversation

gregfromstl
Copy link
Member

@gregfromstl gregfromstl commented May 23, 2025


PR-Codex overview

This PR focuses on updating titles for better clarity and modifying the pagination logic in the routes-table component to directly use routesToRender instead of a derived paginatedRoutes.

Detailed summary

  • Updated title in page.tsx files for improved clarity.
  • Changed the empty state condition to check routesToRender.length instead of paginatedRoutes.length.
  • Replaced paginatedRoutes.map with routesToRender.map in rendering logic.
  • Updated pagination component to use Number(props.searchParams.page) || 1.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

  • New Features
    • Updated page titles and metadata for improved clarity and consistency, including changes from "On-Ramp" to "Onramp" and a new title for the routes page.
  • Refactor
    • Simplified the routes list rendering by removing local pagination logic, now displaying data directly as provided without client-side slicing.

@gregfromstl gregfromstl requested review from a team as code owners May 23, 2025 04:08
Copy link

changeset-bot bot commented May 23, 2025

⚠️ No Changeset found

Latest commit: 6cd64e7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented May 23, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
thirdweb-www ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 4:50am
4 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Skipped (Inspect) May 23, 2025 4:50am
login ⬜️ Skipped (Inspect) May 23, 2025 4:50am
thirdweb_playground ⬜️ Skipped (Inspect) May 23, 2025 4:50am
wallet-ui ⬜️ Skipped (Inspect) May 23, 2025 4:50am

Copy link
Contributor

graphite-app bot commented May 23, 2025

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

Copy link

coderabbitai bot commented May 23, 2025

"""

Walkthrough

The changes update page title strings by standardizing the term "On-Ramp" to "Onramp" and revising the routes page title. Additionally, the client-side pagination logic is removed from the routes table component, shifting responsibility for paginated data to the backend or data-fetching layer.

Changes

File(s) Change Summary
apps/dashboard/src/app/(app)/(dashboard)/(bridge)/bridge/page.tsx Updated the page title string, changing "On-Ramp" to "Onramp" in metadata and OpenGraph title.
apps/dashboard/src/app/(app)/(dashboard)/(bridge)/routes/page.tsx Changed the title from "Routes: Swap, Bridge, and On-Ramp" to "Universal Bridge Routes: Swap, Bridge, and Onramp" in metadata and OpenGraph.
apps/dashboard/src/app/(app)/(dashboard)/(bridge)/routes/components/server/routes-table.tsx Removed local client-side pagination logic; now renders routes directly from the backend/data-fetching layer's paginated result.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Page
    participant DataFetcher

    User->>Page: Request routes page (with pagination params)
    Page->>DataFetcher: Fetch routes (with page, size)
    DataFetcher-->>Page: Return paginated routes
    Page-->>User: Render routes (no client-side slicing)
Loading

Possibly related PRs

Suggested labels

Dashboard
"""

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)
  • TEAM-0000: Entity not found: Issue - Could not find referenced Issue.

📜 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 046da60 and 6cd64e7.

⛔ Files ignored due to path filters (1)
  • apps/dashboard/src/app/(app)/(dashboard)/(bridge)/opengraph-image.png is excluded by !**/*.png
📒 Files selected for processing (3)
  • apps/dashboard/src/app/(app)/(dashboard)/(bridge)/bridge/page.tsx (1 hunks)
  • apps/dashboard/src/app/(app)/(dashboard)/(bridge)/routes/components/server/routes-table.tsx (4 hunks)
  • apps/dashboard/src/app/(app)/(dashboard)/(bridge)/routes/page.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • apps/dashboard/src/app/(app)/(dashboard)/(bridge)/bridge/page.tsx
  • apps/dashboard/src/app/(app)/(dashboard)/(bridge)/routes/page.tsx
  • apps/dashboard/src/app/(app)/(dashboard)/(bridge)/routes/components/server/routes-table.tsx
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: Size
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Lint Packages
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: Analyze (javascript)
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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>, please review it.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

Copy link

codecov bot commented May 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.63%. Comparing base (005acce) to head (6cd64e7).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7136   +/-   ##
=======================================
  Coverage   55.63%   55.63%           
=======================================
  Files         902      902           
  Lines       58190    58190           
  Branches     4098     4098           
=======================================
  Hits        32373    32373           
  Misses      25712    25712           
  Partials      105      105           
Flag Coverage Δ
packages 55.63% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

github-actions bot commented May 23, 2025

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 56.62 KB (0%) 1.2 s (0%) 230 ms (+73.49% 🔺) 1.4 s
thirdweb (cjs) 309.13 KB (0%) 6.2 s (0%) 1.2 s (+3.25% 🔺) 7.4 s
thirdweb (minimal + tree-shaking) 5.69 KB (0%) 114 ms (0%) 107 ms (+1226.13% 🔺) 221 ms
thirdweb/chains (tree-shaking) 531 B (0%) 11 ms (0%) 4 ms (+23.01% 🔺) 14 ms
thirdweb/react (minimal + tree-shaking) 19.5 KB (0%) 390 ms (0%) 98 ms (+294.93% 🔺) 488 ms

Copy link
Member Author

gregfromstl commented May 23, 2025

Merge activity

<!--

## title your PR with this format: "[SDK/Dashboard/Portal] Feature/Fix: Concise title for the changes"

If you did not copy the branch name from Linear, paste the issue tag here (format is TEAM-0000):

## Notes for the reviewer

Anything important to call out? Be sure to also clarify these in your comments.

## How to test

Unit tests, playground, etc.

-->

<!-- start pr-codex -->

---

## PR-Codex overview
This PR focuses on updating titles for better clarity and modifying the pagination logic in the routes table component to directly use `routesToRender`, enhancing the user experience in the dashboard.

### Detailed summary
- Updated `title` in `page.tsx` files for clarity.
- Changed the condition from `paginatedRoutes.length` to `routesToRender.length` in the routes table component.
- Removed pagination logic variables (`activePage`, `pageSize`, `startIndex`, `endIndex`, `paginatedRoutes`).
- Updated pagination component to use `Number(props.searchParams.page) || 1`.

> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`

<!-- end pr-codex -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit

- **New Features**
  - Updated page titles and metadata for improved clarity and consistency, including changes from "On-Ramp" to "Onramp" and a new title for the routes page.
- **Refactor**
  - Simplified the routes list rendering by removing local pagination logic, now displaying data directly as provided without client-side slicing.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@graphite-app graphite-app bot force-pushed the greg/fix-routes-page-crashing branch from 046da60 to 6cd64e7 Compare May 23, 2025 04:43
@vercel vercel bot temporarily deployed to Preview – docs-v2 May 23, 2025 04:43 Inactive
@vercel vercel bot temporarily deployed to Preview – wallet-ui May 23, 2025 04:43 Inactive
@vercel vercel bot temporarily deployed to Preview – login May 23, 2025 04:43 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground May 23, 2025 04:43 Inactive
@graphite-app graphite-app bot merged commit 6cd64e7 into main May 23, 2025
24 checks passed
@graphite-app graphite-app bot removed the merge-queue Adds the pull request to Graphite's merge queue. label May 23, 2025
@graphite-app graphite-app bot deleted the greg/fix-routes-page-crashing branch May 23, 2025 04:51
@vercel vercel bot temporarily deployed to Production – docs-v2 May 23, 2025 04:51 Inactive
@vercel vercel bot temporarily deployed to Production – wallet-ui May 23, 2025 04:51 Inactive
@vercel vercel bot temporarily deployed to Production – thirdweb_playground May 23, 2025 04:51 Inactive
@vercel vercel bot temporarily deployed to Production – login May 23, 2025 04:51 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dashboard Involves changes to the Dashboard.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants