New Crowdin updates#631
Conversation
📝 WalkthroughWalkthroughThis pull request adds comprehensive internationalization support for authorization flows and OpenID Connect scopes across 32 language locales. It introduces 19 new translation keys including error context messages, authorization UI strings (titles, subtitles, loading/success/error states), and OpenID/OAuth scope descriptions. Additionally, some locales receive updates to existing English strings translated into their native languages, while a few undergo key reorganization. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~22 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
frontend/src/lib/i18n/locales/no-NO.json (1)
1-81:⚠️ Potential issue | 🟡 MinorAll strings in
no-NO.jsonare in English — Norwegian translations appear to be missing.This is the Norwegian Bokmål (
no-NO) locale file, yet every string — both existing and newly added — is in English. For a PR titled "New Crowdin updates," this is unexpected. Please verify whether Crowdin has actual Norwegian translations available, or if this file is intentionally kept as an untranslated copy (e.g., as a fallback). If the latter, consider whether shipping an English-onlyno-NOlocale provides any value over simply falling back to the default English locale at runtime.frontend/src/lib/i18n/locales/ro-RO.json (1)
1-81:⚠️ Potential issue | 🟡 MinorAll ro-RO strings are in English (untranslated).
Every value in this Romanian locale file—both existing and newly added—is in English. This is presumably because Romanian translations haven't been contributed on Crowdin yet, and the source strings are exported as fallback. If that's the intended Crowdin workflow (ship source strings until translations arrive), this is fine. Otherwise, these should be translated before merge.
🤖 Fix all issues with AI agents
In `@frontend/src/lib/i18n/locales/pt-PT.json`:
- Around line 63-80: The new authorization and scope strings (authorizeTitle,
authorizeCardTitle, authorizeSubtitle, authorizeSubtitleOAuth,
authorizeLoadingTitle, authorizeLoadingSubtitle, authorizeSuccessTitle,
authorizeSuccessSubtitle, authorizeErrorClientInfo, authorizeErrorMissingParams,
openidScopeName, openidScopeDescription, emailScopeName, emailScopeDescription,
profileScopeName, profileScopeDescription, groupsScopeName,
groupsScopeDescription) are still in English; replace each value with the
correct Portuguese (pt-PT) translation while preserving placeholders like
{{app}} and {{missingParams}} and the JSON string formatting so the locale file
remains valid.
In `@frontend/src/lib/i18n/locales/ru-RU.json`:
- Around line 63-80: The listed i18n entries (authorizeTitle,
authorizeCardTitle, authorizeSubtitle, authorizeSubtitleOAuth,
authorizeLoadingTitle, authorizeLoadingSubtitle, authorizeSuccessTitle,
authorizeSuccessSubtitle, authorizeErrorClientInfo, authorizeErrorMissingParams,
openidScopeName, openidScopeDescription, emailScopeName, emailScopeDescription,
profileScopeName, profileScopeDescription, groupsScopeName,
groupsScopeDescription) are still in English; replace their values with proper
Russian translations in the ru-RU locale JSON so the authorization and OIDC
scope UI is fully localized (ensure placeholders like {{app}} and
{{missingParams}} are preserved exactly).
In `@frontend/src/lib/i18n/locales/tr-TR.json`:
- Line 25: The translation for the key "continueInsecureRedirectSubtitle" in
frontend/src/lib/i18n/locales/tr-TR.json incorrectly says "<code>http</code>
adresinden <code>http</code> adresine" — update the first protocol to
"<code>https</code>" so it reads "<code>https</code> adresinden
<code>http</code> adresine" to match the source en-US string and correctly
indicate an https→http insecure redirect.
🟡 Minor comments (25)
frontend/src/lib/i18n/locales/da-DK.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 MinorTranslate newly added strings to Danish for locale consistency.
The new keys are still in English within
da-DK.json, which will surface English text to Danish users. Please translate these values or move them to the English locale.frontend/src/lib/i18n/locales/fi-FI.json-54-54 (1)
54-54:⚠️ Potential issue | 🟡 MinorUntranslated strings in Finnish locale.
All 19 new keys (
errorSubtitleInfo,authorizeTitle,authorizeCardTitle, …,groupsScopeDescription) contain English text instead of Finnish translations. Every other entry in this file is properly translated to Finnish. These should be translated before merging to maintain a consistent Finnish user experience.Also applies to: 63-80
frontend/src/lib/i18n/locales/pt-PT.json-54-54 (1)
54-54:⚠️ Potential issue | 🟡 MinorUntranslated string in pt-PT locale.
errorSubtitleInfois in English while all surrounding keys are translated to Portuguese.frontend/src/lib/i18n/locales/ar-SA.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 MinorAll new keys are untranslated (English) in the Arabic locale.
The 19 newly added keys (
errorSubtitleInfo,authorizeTitle,authorizeCardTitle, scope names/descriptions, etc.) are all in English rather than Arabic. Since this is a Crowdin-managed PR, these are presumably placeholder strings awaiting community translation. Just flagging for visibility — consider ensuring Arabic translations are contributed before these authorization and OpenID flows are shipped to Arabic-speaking users.frontend/src/lib/i18n/locales/pl-PL.json-78-78 (1)
78-78:⚠️ Potential issue | 🟡 MinorTypo: "porfilu" → "profilu"
"porfilu" appears to be a transposition typo in Polish — the correct word is "profilu".
✏️ Proposed fix
- "profileScopeDescription": "Zezwala aplikacji na dostęp do informacji o porfilu.", + "profileScopeDescription": "Zezwala aplikacji na dostęp do informacji o profilu.",frontend/src/lib/i18n/locales/it-IT.json-54-54 (1)
54-54:⚠️ Potential issue | 🟡 MinorNewly added keys are untranslated (still in English) in the Italian locale.
All 19 new keys (
errorSubtitleInfo,authorizeTitle,authorizeCardTitle, scope names/descriptions, etc.) are English strings in theit-IT.jsonfile. While the existing keys were properly translated to Italian in this PR, these additions appear to be English placeholders.If this is intentional (Crowdin adding keys with English fallbacks pending translation), this is fine — but worth confirming that the translation workflow will fill these in before release.
Also applies to: 63-80
frontend/src/lib/i18n/locales/he-IL.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 MinorAll strings in the
he-ILlocale remain in English.Every new (and existing) value in this Hebrew locale file is in English. If this is intentional as a Crowdin-managed fallback until Hebrew translations arrive, no action needed. Otherwise, Hebrew translations should be provided for these keys.
frontend/src/lib/i18n/locales/fr-FR.json-74-74 (1)
74-74:⚠️ Potential issue | 🟡 MinorUntranslated string:
openidScopeDescriptionis still in English.This value is
"Allows the app to access your OpenID Connect information."while every other entry in this French locale file is translated. This appears to be a Crowdin oversight.Suggested fix
- "openidScopeDescription": "Allows the app to access your OpenID Connect information.", + "openidScopeDescription": "Autorise l'application à accéder à vos informations OpenID Connect.",frontend/src/lib/i18n/locales/vi-VN.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 MinorAll new strings are untranslated (English in vi-VN locale).
The 19 newly added keys (
errorSubtitleInfo,authorizeTitle,authorizeCardTitle, scope descriptions, etc.) all contain English text rather than Vietnamese translations. While some existing keys in this file (e.g.,forgotPasswordTitle,errorSubtitle) are properly translated, none of the new entries are.If this is intentional as part of the Crowdin workflow (untranslated strings defaulting to the source language), this is fine — but it would be worth confirming that these keys are queued for Vietnamese translation on Crowdin.
frontend/src/lib/i18n/locales/uk-UA.json-54-55 (1)
54-55:⚠️ Potential issue | 🟡 MinorNew keys are not translated into Ukrainian.
errorSubtitleInfo(Line 54) and all keys fromauthorizeTitlethroughgroupsScopeDescription(Lines 63–80) remain in English in theuk-UAlocale file. Since this is a Crowdin-sourced PR, these may be awaiting community translation, but shipping them as-is means Ukrainian users will see English strings for the entire authorization/OIDC flow and the error info subtitle.Worth confirming whether the intent is to merge now with English fallbacks and translate later, or to hold until Ukrainian translations are available.
Also applies to: 63-80
frontend/src/lib/i18n/locales/nl-NL.json-55-55 (1)
55-55:⚠️ Potential issue | 🟡 Minor
errorSubtitleis still in English.This is the only remaining untranslated string in the Dutch locale file. Since this PR is updating translations for this locale, this key should be translated to Dutch as well.
Suggested fix
- "errorSubtitle": "An error occurred while trying to perform this action. Please check the console for more information.", + "errorSubtitle": "Er is een fout opgetreden bij het uitvoeren van deze actie. Controleer de console voor meer informatie.",frontend/src/lib/i18n/locales/sr-SP.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 MinorAll new keys are untranslated (English) in the Serbian locale.
Every string added in this file is in English rather than Serbian. If the app doesn't fall back to
en-US.jsonat runtime for missing translations, Serbian-speaking users will see English text for authorization flows and OIDC scope descriptions. If Crowdin is expected to fill these in later, consider whether merging untranslated strings is the intended workflow or if this file should only be updated once actual Serbian translations are available.frontend/src/lib/i18n/locales/ja-JP.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 MinorAll new strings remain untranslated (English) in the Japanese locale.
Every string in this file—both existing and newly added—is in English rather than Japanese. Since this is a Crowdin-managed sync, this is presumably expected behavior where untranslated keys default to the source language. Just flagging for awareness in case Japanese translations were expected to be included in this update.
frontend/src/lib/i18n/locales/pt-BR.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 Minor19 new keys are untranslated (English) in the pt-BR locale.
errorSubtitleInfo(line 54) and all keys fromauthorizeTitlethroughgroupsScopeDescription(lines 63–80) contain English text. Users with the pt-BR locale will see a mix of Portuguese and English in the UI until these are translated.Since this is a Crowdin sync, this is likely expected — but worth confirming that these strings are queued for translation in Crowdin.
frontend/src/lib/i18n/locales/cs-CZ.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 MinorAll 19 new keys are untranslated (English in a Czech locale file).
Every newly added key —
errorSubtitleInfo,authorizeTitlethroughauthorizeErrorMissingParams, andopenidScopeNamethroughgroupsScopeDescription— contains English text rather than Czech translations. Czech-speaking users will see English strings for the entire authorization flow and scope descriptions.If this is intentional as a Crowdin sync that will be followed up with translations, consider tracking the missing Czech translations so they aren't forgotten. Otherwise, these should be translated before merge.
frontend/src/lib/i18n/locales/de-DE.json-54-54 (1)
54-54:⚠️ Potential issue | 🟡 MinorUntranslated English string in German locale.
errorSubtitleInfois in English ("The following error occurred while processing your request:") while all surrounding keys are translated to German. This should be translated.Suggested fix
- "errorSubtitleInfo": "The following error occurred while processing your request:", + "errorSubtitleInfo": "Bei der Verarbeitung Ihrer Anfrage ist folgender Fehler aufgetreten:",frontend/src/lib/i18n/locales/de-DE.json-63-80 (1)
63-80:⚠️ Potential issue | 🟡 MinorAll new authorization and scope keys are untranslated English in the German locale.
18 keys (
authorizeTitlethroughgroupsScopeDescription) are all in English. Since every other string in this file is in German, these should be translated as well.Suggested German translations
- "authorizeTitle": "Authorize", - "authorizeCardTitle": "Continue to {{app}}?", - "authorizeSubtitle": "Would you like to continue to this app? Please carefully review the permissions requested by the app.", - "authorizeSubtitleOAuth": "Would you like to continue to this app?", - "authorizeLoadingTitle": "Loading...", - "authorizeLoadingSubtitle": "Please wait while we load the client information.", - "authorizeSuccessTitle": "Authorized", - "authorizeSuccessSubtitle": "You will be redirected to the app in a few seconds.", - "authorizeErrorClientInfo": "An error occurred while loading the client information. Please try again later.", - "authorizeErrorMissingParams": "The following parameters are missing: {{missingParams}}", - "openidScopeName": "OpenID Connect", - "openidScopeDescription": "Allows the app to access your OpenID Connect information.", - "emailScopeName": "Email", - "emailScopeDescription": "Allows the app to access your email address.", - "profileScopeName": "Profile", - "profileScopeDescription": "Allows the app to access your profile information.", - "groupsScopeName": "Groups", - "groupsScopeDescription": "Allows the app to access your group information." + "authorizeTitle": "Autorisieren", + "authorizeCardTitle": "Weiter zu {{app}}?", + "authorizeSubtitle": "Möchten Sie mit dieser App fortfahren? Bitte überprüfen Sie sorgfältig die von der App angeforderten Berechtigungen.", + "authorizeSubtitleOAuth": "Möchten Sie mit dieser App fortfahren?", + "authorizeLoadingTitle": "Laden...", + "authorizeLoadingSubtitle": "Bitte warten Sie, während wir die Client-Informationen laden.", + "authorizeSuccessTitle": "Autorisiert", + "authorizeSuccessSubtitle": "Sie werden in wenigen Sekunden zur App weitergeleitet.", + "authorizeErrorClientInfo": "Beim Laden der Client-Informationen ist ein Fehler aufgetreten. Bitte versuchen Sie es später erneut.", + "authorizeErrorMissingParams": "Die folgenden Parameter fehlen: {{missingParams}}", + "openidScopeName": "OpenID Connect", + "openidScopeDescription": "Erlaubt der App den Zugriff auf Ihre OpenID Connect Informationen.", + "emailScopeName": "E-Mail", + "emailScopeDescription": "Erlaubt der App den Zugriff auf Ihre E-Mail-Adresse.", + "profileScopeName": "Profil", + "profileScopeDescription": "Erlaubt der App den Zugriff auf Ihre Profilinformationen.", + "groupsScopeName": "Gruppen", + "groupsScopeDescription": "Erlaubt der App den Zugriff auf Ihre Gruppeninformationen."frontend/src/lib/i18n/locales/ru-RU.json-54-54 (1)
54-54:⚠️ Potential issue | 🟡 MinorUntranslated English string in Russian locale.
errorSubtitleInfois in English while every other pre-existing value in this file is in Russian. This should be translated.Proposed fix
- "errorSubtitleInfo": "The following error occurred while processing your request:", + "errorSubtitleInfo": "При обработке вашего запроса произошла следующая ошибка:",frontend/src/lib/i18n/locales/sv-SE.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 MinorAll newly added strings are in English, not translated to Swedish.
This is the
sv-SE(Swedish) locale file, but every new key added in this PR (errorSubtitleInfo,authorizeTitle,authorizeCardTitle,authorizeSubtitle,authorizeSubtitleOAuth,authorizeLoadingTitle,authorizeLoadingSubtitle,authorizeSuccessTitle,authorizeSuccessSubtitle,authorizeErrorClientInfo,authorizeErrorMissingParams,openidScopeName,openidScopeDescription,emailScopeName,emailScopeDescription,profileScopeName,profileScopeDescription,groupsScopeName,groupsScopeDescription) contains English text rather than Swedish translations. Swedish-speaking users will see English strings for the entire authorization flow and scope descriptions.Several pre-existing keys also remain untranslated (e.g., lines 18–19, 23, 26–27, 33–48), so this appears to be a broader translation gap. Consider prioritizing Swedish translations for these keys in the next Crowdin sync.
frontend/src/lib/i18n/locales/hu-HU.json-31-31 (1)
31-31:⚠️ Potential issue | 🟡 MinorSame formality inconsistency here — informal "Kijelentkeztél" should match the formal tone used elsewhere.
Proposed fix
- "logoutSuccessSubtitle": "Kijelentkeztél", + "logoutSuccessSubtitle": "Sikeresen kijelentkezett",frontend/src/lib/i18n/locales/hu-HU.json-10-10 (1)
10-10:⚠️ Potential issue | 🟡 MinorInconsistent formality (te/ön) in Hungarian translations.
Line 10 uses the informal register ("próbálkoztál", "Próbáld"), while surrounding translations (e.g., lines 9, 29, 39, 49) use the formal register ("ellenőrizze", "Próbálja", "próbálja"). Pick one form consistently — typically formal ("Ön") for application UI — and apply it throughout.
Proposed fix
- "loginFailRateLimit": "Túl sokszor próbálkoztál bejelentkezni. Próbáld újra később", + "loginFailRateLimit": "Túl sokszor próbálkozott bejelentkezni. Próbálja újra később",frontend/src/lib/i18n/locales/tr-TR.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 MinorNew keys (and
errorSubtitle) are not translated to Turkish.While many existing keys received proper Turkish translations in this update, all newly added keys (
errorSubtitleInfo,authorizeTitlethroughgroupsScopeDescription) anderrorSubtitle(line 55) remain in English.frontend/src/lib/i18n/locales/es-ES.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 MinorNew keys are not translated to Spanish.
All newly added keys remain in English. Additionally, several pre-existing keys (e.g., lines 17–19, 23, 26–27, 48, 56–61) are also still in English — may be worth addressing those in the same Crowdin translation pass.
frontend/src/lib/i18n/locales/zh-TW.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 MinorNew keys are not translated to Traditional Chinese.
All newly added keys (
errorSubtitleInfo,authorizeTitlethroughgroupsScopeDescription) contain English strings instead of Traditional Chinese translations. The existing strings in this file are fully localized, so these stand out as untranslated placeholders. If Crowdin hasn't received translations yet, consider holding off on merging these intozh-TW.jsonuntil translations are available, or ensure they fall back toen-USat runtime rather than appearing as raw English in a Chinese UI.frontend/src/lib/i18n/locales/zh-CN.json-54-80 (1)
54-80:⚠️ Potential issue | 🟡 MinorNew keys are not translated to Simplified Chinese.
Same as
zh-TW.json— all newly added keys contain English text while the rest of the file is fully localized in Simplified Chinese. These should be translated before shipping to avoid a mixed-language UI.
🧹 Nitpick comments (1)
frontend/src/lib/i18n/locales/hu-HU.json (1)
2-2: Several pre-existing keys also remain in English.
loginTitle,loginOauthFailTitle,loginOauthFailSubtitle,loginOauthSuccessSubtitle, and the OAuth auto-redirect keys are still untranslated. Since this PR is touching the file anyway, it would be a good opportunity to translate these as well.Also applies to: 13-14, 16-19
| "authorizeTitle": "Authorize", | ||
| "authorizeCardTitle": "Continue to {{app}}?", | ||
| "authorizeSubtitle": "Would you like to continue to this app? Please carefully review the permissions requested by the app.", | ||
| "authorizeSubtitleOAuth": "Would you like to continue to this app?", | ||
| "authorizeLoadingTitle": "Loading...", | ||
| "authorizeLoadingSubtitle": "Please wait while we load the client information.", | ||
| "authorizeSuccessTitle": "Authorized", | ||
| "authorizeSuccessSubtitle": "You will be redirected to the app in a few seconds.", | ||
| "authorizeErrorClientInfo": "An error occurred while loading the client information. Please try again later.", | ||
| "authorizeErrorMissingParams": "The following parameters are missing: {{missingParams}}", | ||
| "openidScopeName": "OpenID Connect", | ||
| "openidScopeDescription": "Allows the app to access your OpenID Connect information.", | ||
| "emailScopeName": "Email", | ||
| "emailScopeDescription": "Allows the app to access your email address.", | ||
| "profileScopeName": "Profile", | ||
| "profileScopeDescription": "Allows the app to access your profile information.", | ||
| "groupsScopeName": "Groups", | ||
| "groupsScopeDescription": "Allows the app to access your group information." |
There was a problem hiding this comment.
All new authorization and scope strings are untranslated (English in pt-PT locale).
All 18 newly added keys (authorizeTitle through groupsScopeDescription) contain English text. Since this is the Portuguese (Portugal) locale, these should be translated to Portuguese — the same way lines 2–62 are. As-is, Portuguese users will see an abrupt mix of Portuguese and English in the UI.
🤖 Prompt for AI Agents
In `@frontend/src/lib/i18n/locales/pt-PT.json` around lines 63 - 80, The new
authorization and scope strings (authorizeTitle, authorizeCardTitle,
authorizeSubtitle, authorizeSubtitleOAuth, authorizeLoadingTitle,
authorizeLoadingSubtitle, authorizeSuccessTitle, authorizeSuccessSubtitle,
authorizeErrorClientInfo, authorizeErrorMissingParams, openidScopeName,
openidScopeDescription, emailScopeName, emailScopeDescription, profileScopeName,
profileScopeDescription, groupsScopeName, groupsScopeDescription) are still in
English; replace each value with the correct Portuguese (pt-PT) translation
while preserving placeholders like {{app}} and {{missingParams}} and the JSON
string formatting so the locale file remains valid.
| "authorizeTitle": "Authorize", | ||
| "authorizeCardTitle": "Continue to {{app}}?", | ||
| "authorizeSubtitle": "Would you like to continue to this app? Please carefully review the permissions requested by the app.", | ||
| "authorizeSubtitleOAuth": "Would you like to continue to this app?", | ||
| "authorizeLoadingTitle": "Loading...", | ||
| "authorizeLoadingSubtitle": "Please wait while we load the client information.", | ||
| "authorizeSuccessTitle": "Authorized", | ||
| "authorizeSuccessSubtitle": "You will be redirected to the app in a few seconds.", | ||
| "authorizeErrorClientInfo": "An error occurred while loading the client information. Please try again later.", | ||
| "authorizeErrorMissingParams": "The following parameters are missing: {{missingParams}}", | ||
| "openidScopeName": "OpenID Connect", | ||
| "openidScopeDescription": "Allows the app to access your OpenID Connect information.", | ||
| "emailScopeName": "Email", | ||
| "emailScopeDescription": "Allows the app to access your email address.", | ||
| "profileScopeName": "Profile", | ||
| "profileScopeDescription": "Allows the app to access your profile information.", | ||
| "groupsScopeName": "Groups", | ||
| "groupsScopeDescription": "Allows the app to access your group information." |
There was a problem hiding this comment.
All new authorization and OIDC scope keys are untranslated (English in the Russian locale).
Every key from authorizeTitle through groupsScopeDescription is in English. In a ru-RU locale file these must be in Russian to provide actual localization. As-is, Russian-speaking users will see a jarring mix of Russian and English UI text during authorization flows.
Suggested Russian translations
- "authorizeTitle": "Authorize",
- "authorizeCardTitle": "Continue to {{app}}?",
- "authorizeSubtitle": "Would you like to continue to this app? Please carefully review the permissions requested by the app.",
- "authorizeSubtitleOAuth": "Would you like to continue to this app?",
- "authorizeLoadingTitle": "Loading...",
- "authorizeLoadingSubtitle": "Please wait while we load the client information.",
- "authorizeSuccessTitle": "Authorized",
- "authorizeSuccessSubtitle": "You will be redirected to the app in a few seconds.",
- "authorizeErrorClientInfo": "An error occurred while loading the client information. Please try again later.",
- "authorizeErrorMissingParams": "The following parameters are missing: {{missingParams}}",
- "openidScopeName": "OpenID Connect",
- "openidScopeDescription": "Allows the app to access your OpenID Connect information.",
- "emailScopeName": "Email",
- "emailScopeDescription": "Allows the app to access your email address.",
- "profileScopeName": "Profile",
- "profileScopeDescription": "Allows the app to access your profile information.",
- "groupsScopeName": "Groups",
- "groupsScopeDescription": "Allows the app to access your group information."
+ "authorizeTitle": "Авторизация",
+ "authorizeCardTitle": "Продолжить в {{app}}?",
+ "authorizeSubtitle": "Хотите продолжить в это приложение? Пожалуйста, внимательно ознакомьтесь с запрашиваемыми разрешениями.",
+ "authorizeSubtitleOAuth": "Хотите продолжить в это приложение?",
+ "authorizeLoadingTitle": "Загрузка...",
+ "authorizeLoadingSubtitle": "Пожалуйста, подождите, пока мы загружаем информацию о клиенте.",
+ "authorizeSuccessTitle": "Авторизовано",
+ "authorizeSuccessSubtitle": "Вы будете перенаправлены в приложение через несколько секунд.",
+ "authorizeErrorClientInfo": "Произошла ошибка при загрузке информации о клиенте. Попробуйте позже.",
+ "authorizeErrorMissingParams": "Отсутствуют следующие параметры: {{missingParams}}",
+ "openidScopeName": "OpenID Connect",
+ "openidScopeDescription": "Разрешает приложению доступ к вашей информации OpenID Connect.",
+ "emailScopeName": "Электронная почта",
+ "emailScopeDescription": "Разрешает приложению доступ к вашему адресу электронной почты.",
+ "profileScopeName": "Профиль",
+ "profileScopeDescription": "Разрешает приложению доступ к информации вашего профиля.",
+ "groupsScopeName": "Группы",
+ "groupsScopeDescription": "Разрешает приложению доступ к информации о ваших группах."🤖 Prompt for AI Agents
In `@frontend/src/lib/i18n/locales/ru-RU.json` around lines 63 - 80, The listed
i18n entries (authorizeTitle, authorizeCardTitle, authorizeSubtitle,
authorizeSubtitleOAuth, authorizeLoadingTitle, authorizeLoadingSubtitle,
authorizeSuccessTitle, authorizeSuccessSubtitle, authorizeErrorClientInfo,
authorizeErrorMissingParams, openidScopeName, openidScopeDescription,
emailScopeName, emailScopeDescription, profileScopeName,
profileScopeDescription, groupsScopeName, groupsScopeDescription) are still in
English; replace their values with proper Russian translations in the ru-RU
locale JSON so the authorization and OIDC scope UI is fully localized (ensure
placeholders like {{app}} and {{missingParams}} are preserved exactly).
| "continueRedirectingSubtitle": "Kısa süre içinde uygulamaya yönlendirileceksiniz", | ||
| "continueRedirectManually": "Beni manuel olarak yönlendir", | ||
| "continueInsecureRedirectTitle": "Güvenli olmayan yönlendirme", | ||
| "continueInsecureRedirectSubtitle": "<code>http</code> adresinden <code>http</code> adresine yönlendirme yapmaya çalışıyorsunuz, bu güvenli değil. Devam etmek istediğinizden emin misiniz?", |
There was a problem hiding this comment.
Bug: Turkish translation says http → http instead of https → http.
The insecure redirect warning should indicate a redirect from https to http. The first <code>http</code> should be <code>https</code>, matching the source string in en-US.json.
Proposed fix
- "continueInsecureRedirectSubtitle": "<code>http</code> adresinden <code>http</code> adresine yönlendirme yapmaya çalışıyorsunuz, bu güvenli değil. Devam etmek istediğinizden emin misiniz?",
+ "continueInsecureRedirectSubtitle": "<code>https</code> adresinden <code>http</code> adresine yönlendirme yapmaya çalışıyorsunuz, bu güvenli değil. Devam etmek istediğinizden emin misiniz?",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "continueInsecureRedirectSubtitle": "<code>http</code> adresinden <code>http</code> adresine yönlendirme yapmaya çalışıyorsunuz, bu güvenli değil. Devam etmek istediğinizden emin misiniz?", | |
| "continueInsecureRedirectSubtitle": "<code>https</code> adresinden <code>http</code> adresine yönlendirme yapmaya çalışıyorsunuz, bu güvenli değil. Devam etmek istediğinizden emin misiniz?", |
🤖 Prompt for AI Agents
In `@frontend/src/lib/i18n/locales/tr-TR.json` at line 25, The translation for the
key "continueInsecureRedirectSubtitle" in
frontend/src/lib/i18n/locales/tr-TR.json incorrectly says "<code>http</code>
adresinden <code>http</code> adresine" — update the first protocol to
"<code>https</code>" so it reads "<code>https</code> adresinden
<code>http</code> adresine" to match the source en-US string and correctly
indicate an https→http insecure redirect.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #631 +/- ##
=======================================
Coverage 16.16% 16.16%
=======================================
Files 45 45
Lines 3427 3427
=======================================
Hits 554 554
Misses 2816 2816
Partials 57 57 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
1 participant
Summary by CodeRabbit