## Summary
- always load the fallback language on application startup
- load the user's selected language afterwards if it differs from the fallback language
- ensure fallback translations are available immediately during the initial load
## Related issues
Closes: #130
jakob.gregory
added this to the 0.1.0 milestone 2026-07-21 19:09:58 +02:00
This check is not necessary. loadLanguage already checks whether a language has already been loaded. If the language preferred by the user is the same as the fallback language, it is not redundantly fetched.
This check is not necessary. `loadLanguage` already checks whether a language has already been loaded. If the language preferred by the user is the same as the fallback language, it is not redundantly fetched.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Related issues
Closes: #130
@@ -27,1 +27,3 @@await loadLanguage(getCurrentLanguage())await loadLanguage(fallbackLocale)const currentLanguage = getCurrentLanguage()This check is not necessary.
loadLanguagealready checks whether a language has already been loaded. If the language preferred by the user is the same as the fallback language, it is not redundantly fetched.@@ -25,3 +25,3 @@(async () => {await loadLanguage(getCurrentLanguage())await loadLanguage(fallbackLocale)Please use a semicolon at the end of the line.
I will fix that.