Justin Edmund
3d67622353
## 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>
19 lines
875 B
TypeScript
19 lines
875 B
TypeScript
import {getRequestConfig} from 'next-intl/server'
|
|
import {locales, defaultLocale, type Locale} from '../i18n.config'
|
|
|
|
// next-intl v4: global request config used by getMessages()
|
|
export default getRequestConfig(async ({requestLocale}) => {
|
|
let locale = (await requestLocale) as Locale | null;
|
|
if (!locale || !locales.includes(locale)) {
|
|
locale = defaultLocale;
|
|
}
|
|
|
|
// Load only i18n namespaces; exclude content data with dotted keys
|
|
const common = (await import(`../public/locales/${locale}/common.json`)).default;
|
|
const about = (await import(`../public/locales/${locale}/about.json`)).default;
|
|
// Re-include updates.json now that dotted version keys have been renamed (e.g., v1_2_1)
|
|
const updates = (await import(`../public/locales/${locale}/updates.json`)).default;
|
|
const messages = {common, about, updates} as const;
|
|
|
|
return {locale, messages};
|
|
});
|