closes#22372
Co-authored-by: Erik Jan de Wit <erikjan.dewit@gmail.com>
Co-authored-by: Pedro Igor <pigor.craveiro@gmail.com>
Co-authored-by: Michal Hajas <mhajas@redhat.com>
* added some user profile tests
* added some user profile tests
* added more tests for user profile and attributes
* improved tests for user profile
* removed videos
* refactor and improvement
* improved tests
---------
Co-authored-by: Agnieszka Gancarczyk <agancarc@redhat.com>
* merge all namespaces into one
added fallback namespace to the configuration to minimize
changes to the keys
* small fix
* Fix the broken `OverridesBackend`
* remove stray console log
* restore ns argument
* PR review
* merge main
---------
Co-authored-by: Jon Koops <jonkoops@gmail.com>
* initial version of the "known" annotation picker
* fixed empty value
* add input type select when validator is options
* fixed test
* Update js/apps/admin-ui/public/locales/en/common.json
Co-authored-by: Jon Koops <jonkoops@gmail.com>
---------
Co-authored-by: Jon Koops <jonkoops@gmail.com>
- the prio of messages is now as follows for all themes (RL = realm localization, T = Theme i18n files): RL <variant> > T <variant> > RL <region> > T <region> > RL <language> > T <language> > RL en > T en
- centralize the message resolving logic in helper methods in LocaleUtil and use it for all themes, add unit tests in LocaleUtilTest
- add basic integration tests to check whether realm localization can be used in all supported contexts:
- Account UI V2: org.keycloak.testsuite.ui.account2.InternationalizationTest
- Login theme: LoginPageTest
- Email theme: EmailTest
- deprecate the param useRealmDefaultLocaleFallback=true of endpoint /admin/realms/{realm}/localization/{locale}, because it does not resolve fallbacks as expected and is no longer used in admin-ui v2
- fix locale selection in DefaultLocaleSelectorProvider that a supported region (like "de-CH") will no longer selected instead of a supported language (like "de"), when just the language is requested, add corresponding unit tests
- improvements regarding message resolving in Admin UI V2:
- add cypress test i18n_test.spec.ts, which checks the fallback implementation
- log a warning instead of an error, when messages for some languages/namespaces cannot be loaded (the page will probably work with fallbacks in that case)
Closes#15845
