fix: Make page params async and simplify API route#537
Closed
pmilano1 wants to merge 1 commit into
Closed
Conversation
- Page component now awaits params (Next.js 15) - API route queries database directly (no GraphQL client issues) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
pmilano1
force-pushed
the
fix/page-params-async
branch
from
f6bf5b8 to
6922fcb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
undefinedbeing passed as the family parameterRoot Cause
The page component wasn't awaiting the params Promise, so
undefinedwas being passed to the client component, resulting in/api/family-notes/undefined404 errors.Changes
app/family-notes/[family]/page.tsx: Made async, await paramsapp/api/family-notes/[family]/route.ts: Query database directly, simplified logicFixes the family notes 404 issue.
🤖 Generated with Claude Code