hensei-web/components/party
Justin Edmund 8ea7c95446 fix: import useSearchParams from next/navigation instead of next-intl
- Remove useSearchParams from next-intl's createNavigation exports
- Import useSearchParams directly from next/navigation in client components
- Fixes "useSearchParams is not a function" error
- Affected components: TeamsPageClient, ProfilePageClient, SavedPageClient, PartyHeader

next-intl's createNavigation doesn't export useSearchParams, it must be
imported from Next.js directly

🤖 Generated with Claude Code
https://claude.ai/code

Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-02 20:41:21 -07:00
..
EditPartyModal refactor: migrate all components from next-i18next to next-intl 2025-09-02 19:48:04 -07:00
Party refactor: migrate all components from next-i18next to next-intl 2025-09-02 19:48:04 -07:00
PartyDropdown refactor: migrate all components from next-i18next to next-intl 2025-09-02 19:48:04 -07:00
PartyFooter refactor: migrate all components from next-i18next to next-intl 2025-09-02 19:48:04 -07:00
PartyHead refactor: migrate all components from next-i18next to next-intl 2025-09-02 19:48:04 -07:00
PartyHeader fix: import useSearchParams from next/navigation instead of next-intl 2025-09-02 20:41:21 -07:00
PartySegmentedControl refactor: migrate all components from next-i18next to next-intl 2025-09-02 19:48:04 -07:00
PartyVisibilityDialog refactor: migrate all components from next-i18next to next-intl 2025-09-02 19:48:04 -07:00