fixes extensions page to list all extensions #341 - #1
Conversation
|
Warning Review limit reached
More reviews will be available in 28 minutes and 45 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThis PR adds a packages explorer page accessible via ChangesPackages Explorer Page
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a new Packages Explorer page (website/pages/packages.tsx) that allows users to search, filter, sort, and paginate database packages from database.dev. It also adds a link to this page in the navigation bar and updates TypeScript configurations. Feedback on the changes suggests refactoring the raw fetch call in the packages page to use the project's configured supabase client and wrapping it in useCallback to prevent unnecessary recreations and address potential dependency issues.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
JesseVent
changed the title
0f716a9 to
498f589
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
website/pages/packages.tsx (1)
64-79: ⚡ Quick winPrefer the existing typed
searchPackagesdata helper instead of duplicating raw RPC fetch logic.This page reimplements request headers/error handling and bypasses the shared typed query path, which increases contract drift risk. Reusing
website/data/packages/packages-search-query.tskeeps API behavior and typing consistent.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@website/pages/packages.tsx` around lines 64 - 79, The fetchPackages function duplicates a raw RPC fetch with inline headers and error handling instead of using the typed shared helper; replace the body of fetchPackages to call the existing searchPackages helper from website/data/packages/packages-search-query.ts (import it if missing), pass the same parameters (e.g., handle: ''), and propagate its typed result and errors into setLoading/setError/state updates so you keep centralized typing, headers and error behavior managed by searchPackages.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@website/next-env.d.ts`:
- Line 4: Update the import in next-env.d.ts to use the stable generated routes
proxy path instead of the dev-only one: replace the import string
"./.next/dev/types/routes.d.ts" with "./.next/types/routes.d.ts" so typed routes
are found in CI and during next build/type-check; modify the import statement in
the file where it currently references the dev path (the import at the top of
next-env.d.ts) to point to the stable proxy path.
In `@website/pages/packages.tsx`:
- Around line 28-40: The Package interface is non-nullable while the
search_packages RPC can return nullable fields, causing runtime errors (e.g.,
calls like toLowerCase, substring, link construction, and
dayjs(pkg.created_at)); update handling so either (A) expand the Package type to
make nullable fields optional/nullable to match the RPC, or (B) normalize RPC
results before storing by mapping the search_packages response to a sanitized
object (e.g., coerce nulls to '' or a safe default and ensure created_at is a
valid string) and then call setPackages(...) with the sanitized array; reference
the Package interface, the search_packages response mapping, and the setPackages
call when making the change.
---
Nitpick comments:
In `@website/pages/packages.tsx`:
- Around line 64-79: The fetchPackages function duplicates a raw RPC fetch with
inline headers and error handling instead of using the typed shared helper;
replace the body of fetchPackages to call the existing searchPackages helper
from website/data/packages/packages-search-query.ts (import it if missing), pass
the same parameters (e.g., handle: ''), and propagate its typed result and
errors into setLoading/setError/state updates so you keep centralized typing,
headers and error behavior managed by searchPackages.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: ee1605b9-3d64-48ec-8136-e10f34e575f3
📒 Files selected for processing (4)
website/components/layouts/Navbar.tsxwebsite/next-env.d.tswebsite/pages/packages.tsxwebsite/tsconfig.json
1 participant
Feat: Add Interactive Packages Explorer Page
Description
This pull request adds a new Packages Explorer page (
/packages) that connects directly to the registry's public RPC API (rpc/search_packages) to display a complete, searchable, sortable, and filterable table of all database packages.Problem & Justification
Currently, the database.dev website only displays a handful of "Popular packages" on the homepage. There is no way for developers to browse, search, or inspect the full catalog of packages hosted in the registry.
pg_cron), and quickly copy the install command.Key Features Implemented:
Summary by CodeRabbit