-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Language selector options are not translated #1043
Comments
Huh, the component should rerender if the textresources change. Do you have an app with custom languages I can take a look at? |
@bjosttveit if you want to see the behavior: https://udir.apps.tt02.altinn.no/udir/pbu-test-anonym and username: t-gangs-105 password: srxn9 |
Yeah that component was recently switched out to use digdir/designsystem |
Weird, I managed to reproduce this in my own app. But only by omitting the language name in some resource files. It worked for me as long as each language name was defined in all of the resource files. |
Interessting I can try that! |
That doesn't seem to help for me... It seems wierd that it has to be defined in all the resourcefiles because it just fetches one language resource file at a time? It could behave different in local development. Our demoapplication (stateless) show it correct after a refresh: https://udir.apps.tt02.altinn.no/udir/pbu-test-demo?survey=survey-5-aarstrinn5 |
That link worked without refresh for me |
This seemes to be fixed |
Description of the bug
If you have added custom language files their translations are not shown. If the app is stateless it helps to refresh the page for some reason. It seemes to be related to this issue i think: digdir/designsystemet#180
Steps To Reproduce
Additional Information
The textresources are probably fetched after the languageSelector has been rendered so the options will only use the key instead of the textresources value.
The text was updated successfully, but these errors were encountered: