Skip to content

fix(frontend): connect Settings DisplaySection language selector to next-intl routing (#2010) - #2034

Open
aazminu wants to merge 1 commit into
LabsCrypt:mainfrom
aazminu:fix/2010-settings-display-language-selector
Open

aazminu wants to merge 1 commit into
LabsCrypt:mainfrom
aazminu:fix/2010-settings-display-language-selector

Conversation

@aazminu

@aazminu aazminu commented Oct 18, 2026

Copy link
Copy Markdown

Summary

Fixes #2010
Closes #2010
/claim #2010

  • Connect DisplaySection's language selector in frontend/src/app/[locale]/settings/page.tsx to useLocale() and useRouter() / usePathname() (matching LanguageSwitcher.tsx) so selecting a language updates the active next-intl locale route.
  • Restrict the language selector options to the supported locales (en, es, tl) and remove the outdated fallback warning banner.
  • Update frontend/src/app/[locale]/settings/page.test.tsx to verify the supported locale options (en, es, tl), absence of the stale fallback banner, and router.replace locale navigation.

Settlement Details

  • USDT / USDC Wallet (EVM): 0x9a51790aC01c54184bcFa067bC38f7F0E7C6F6B6

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug][Frontend] Settings DisplaySection language selector uses local dummy state and outdated language list

1 participant