## Summary
- Fixed translation key format compatibility with next-intl
- Fixed pluralization format from i18next to next-intl format
- Fixed dynamic translation key error handling
- Updated server components to match API response structure
- Fixed useSearchParams import location
## Changes
- Changed pluralization from `{{count}} items` to `{count} items` format
- Added proper error handling for missing translation keys
- Fixed import paths for next-intl hooks
- Fixed PartyPageClient trying to set non-existent appState.parties
## Test plan
- [x] Verified translations render correctly
- [x] Tested pluralization works with different counts
- [x] Confirmed no console errors about missing translations
- [x] Tested party page functionality
🤖 Generated with [Claude Code](https://claude.ai/code)
---------
Co-authored-by: Claude <noreply@anthropic.com>
29 lines
831 B
TypeScript
29 lines
831 B
TypeScript
import { Metadata } from 'next'
|
|
import { Link } from '~/i18n/navigation'
|
|
import { getTranslations } from 'next-intl/server'
|
|
|
|
export const metadata: Metadata = {
|
|
title: 'Page not found / granblue.team',
|
|
description: 'The page you were looking for could not be found'
|
|
}
|
|
|
|
export default async function NotFound() {
|
|
const t = await getTranslations('common')
|
|
|
|
return (
|
|
<div className="error-container">
|
|
<div className="error-content">
|
|
<h1>Not Found</h1>
|
|
<p>The page you're looking for couldn't be found</p>
|
|
<div className="error-actions">
|
|
<Link href="/new" className="button primary">
|
|
Create a new party
|
|
</Link>
|
|
<Link href="/teams" className="button secondary">
|
|
Browse teams
|
|
</Link>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
)
|
|
}
|