GPT-5 finding
Misleading comment and incorrect typing: searchParams is not a Promise in Next.js App Router
lowdocs-gaphigh
- apps/web/app/receipts/page.tsx:38-41
- apps/web/app/receipts/page.tsx:44-49
In Next.js App Router, page components receive searchParams as a plain object, not a Promise. Awaiting a non-Promise value works at runtime but the comment is incorrect and the prop type is misleading. This can confuse maintainers and cause friction when adopting official Next.js types or tooling that expects the correct signature.
Recommendation
Update the comment and types: - Change the prop type to { searchParams: SearchParams } (object, not Promise) - Remove the unnecessary await and use const params = searchParams; - Adjust the comment to reflect the correct contract. This keeps typings aligned with Next.js and avoids confusion.