-
Notifications
You must be signed in to change notification settings - Fork 535
[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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
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. |
""" WalkthroughThe 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
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)
Possibly related PRs
Suggested labels
Warning Review ran into problems🔥 ProblemsErrors were encountered while retrieving linked issues. Errors (1)
📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (3)
⏰ Context from checks skipped due to timeout of 90000ms (6)
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
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
🚀 New features to boost your workflow:
|
size-limit report 📦
|
d4249c6
to
046da60
Compare
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 -->
046da60
to
6cd64e7
Compare
PR-Codex overview
This PR focuses on updating titles for better clarity and modifying the pagination logic in the
routes-table
component to directly useroutesToRender
instead of a derivedpaginatedRoutes
.Detailed summary
page.tsx
files for improved clarity.routesToRender.length
instead ofpaginatedRoutes.length
.paginatedRoutes.map
withroutesToRender.map
in rendering logic.Number(props.searchParams.page) || 1
.Summary by CodeRabbit