Merged
Conversation
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
33 issues found across 62 files
Prompt for AI agents (all 33 issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name="packages/twenty-front/src/locales/tr-TR.po">
<violation number="1" location="packages/twenty-front/src/locales/tr-TR.po:7952">
P2: Missing Turkish translation for "Rich Text". The `msgstr` is empty, so Turkish users will see the English text instead.</violation>
<violation number="2" location="packages/twenty-front/src/locales/tr-TR.po:9238">
P2: Missing Turkish translation for "Text Colors". The `msgstr` is empty, so Turkish users will see the English text instead.</violation>
</file>
<file name="packages/twenty-front/src/locales/zh-CN.po">
<violation number="1" location="packages/twenty-front/src/locales/zh-CN.po:1590">
P2: Missing Chinese translation for "Text Colors". This should be translated (e.g., "文本颜色") to maintain consistency with other translated strings in this locale file.</violation>
<violation number="2" location="packages/twenty-front/src/locales/zh-CN.po:1590">
P2: Missing Chinese translation for "Rich Text". This should be translated (e.g., "富文本") to maintain consistency with other translated strings in this locale file.</violation>
</file>
<file name="packages/twenty-front/src/locales/es-ES.po">
<violation number="1" location="packages/twenty-front/src/locales/es-ES.po:1590">
P2: Missing Spanish translation for "Background Colors". Empty `msgstr` means users will see untranslated English text.</violation>
<violation number="2" location="packages/twenty-front/src/locales/es-ES.po:7952">
P2: Missing Spanish translation for "Rich Text". Empty `msgstr` means users will see untranslated English text.</violation>
<violation number="3" location="packages/twenty-front/src/locales/es-ES.po:9238">
P2: Missing Spanish translation for "Text Colors". Empty `msgstr` means users will see untranslated English text.</violation>
</file>
<file name="packages/twenty-front/src/locales/vi-VN.po">
<violation number="1" location="packages/twenty-front/src/locales/vi-VN.po:1590">
P2: Missing Vietnamese translation for "Text Colors". This will cause the UI to fall back to English for Vietnamese users. Consider adding a translation such as "Màu văn bản".</violation>
<violation number="2" location="packages/twenty-front/src/locales/vi-VN.po:1590">
P2: Missing Vietnamese translation for "Rich Text". This will cause the UI to fall back to English for Vietnamese users. Consider adding a translation such as "Văn bản phong phú".</violation>
<violation number="3" location="packages/twenty-front/src/locales/vi-VN.po:1590">
P2: Missing Vietnamese translation for "Background Colors". This will cause the UI to fall back to English for Vietnamese users. Consider adding a translation such as "Màu nền".</violation>
</file>
<file name="packages/twenty-front/src/locales/cs-CZ.po">
<violation number="1" location="packages/twenty-front/src/locales/cs-CZ.po:9238">
P2: Missing Czech translation for "Text Colors". Consider adding the translation: `msgstr "Barvy textu"`</violation>
</file>
<file name="packages/twenty-front/src/locales/hu-HU.po">
<violation number="1" location="packages/twenty-front/src/locales/hu-HU.po:1590">
P2: Missing Hungarian translation for "Background Colors". Empty `msgstr` means users will see English text. Consider adding the Hungarian translation: `msgstr "Háttérszínek"`</violation>
<violation number="2" location="packages/twenty-front/src/locales/hu-HU.po:7952">
P2: Missing Hungarian translation for "Rich Text". Empty `msgstr` means users will see English text. Consider adding the Hungarian translation: `msgstr "Formázott szöveg"`</violation>
<violation number="3" location="packages/twenty-front/src/locales/hu-HU.po:9238">
P2: Missing Hungarian translation for "Text Colors". Empty `msgstr` means users will see English text. Consider adding the Hungarian translation: `msgstr "Szövegszínek"`</violation>
</file>
<file name="packages/twenty-front/src/locales/sr-Cyrl.po">
<violation number="1" location="packages/twenty-front/src/locales/sr-Cyrl.po:1590">
P2: Missing translation for 'Rich Text'. The `msgstr` is empty, which will cause Serbian Cyrillic users to see English text. Consider adding the Serbian Cyrillic translation: `"Богат текст"` or `"Обогаћени текст"`.</violation>
<violation number="2" location="packages/twenty-front/src/locales/sr-Cyrl.po:1590">
P2: Missing translation for 'Background Colors'. The `msgstr` is empty, which will cause Serbian Cyrillic users to see English text. Consider adding the Serbian Cyrillic translation: `"Боје позадине"`.</violation>
<violation number="3" location="packages/twenty-front/src/locales/sr-Cyrl.po:1590">
P2: Missing translation for 'Text Colors'. The `msgstr` is empty, which will cause Serbian Cyrillic users to see English text. Consider adding the Serbian Cyrillic translation: `"Боје текста"`.</violation>
</file>
<file name="packages/twenty-front/src/locales/ar-SA.po">
<violation number="1" location="packages/twenty-front/src/locales/ar-SA.po:1590">
P2: Missing Arabic translation for "Background Colors". Empty `msgstr` will cause English text to display for Arabic users. Consider adding the Arabic translation: `msgstr "ألوان الخلفية"`</violation>
<violation number="2" location="packages/twenty-front/src/locales/ar-SA.po:9238">
P2: Missing Arabic translation for "Text Colors". Empty `msgstr` will cause English text to display for Arabic users. Consider adding the Arabic translation: `msgstr "ألوان النص"`</violation>
</file>
<file name="packages/twenty-front/src/locales/ca-ES.po">
<violation number="1" location="packages/twenty-front/src/locales/ca-ES.po:1590">
P2: Missing Catalan translation for "Background Colors". Consider providing the translation (e.g., "Colors de fons") to ensure proper localization for Catalan users.</violation>
</file>
<file name="packages/twenty-front/src/locales/ja-JP.po">
<violation number="1" location="packages/twenty-front/src/locales/ja-JP.po:1590">
P2: Missing Japanese translation for "Background Colors". Empty `msgstr` means Japanese users will see English text instead of localized content.</violation>
</file>
<file name="packages/twenty-front/src/locales/ro-RO.po">
<violation number="1" location="packages/twenty-front/src/locales/ro-RO.po:1590">
P2: Missing Romanian translation for "Text Colors". Empty `msgstr` will cause the UI to display English text for Romanian users.</violation>
<violation number="2" location="packages/twenty-front/src/locales/ro-RO.po:1590">
P2: Missing Romanian translation for "Rich Text". Empty `msgstr` will cause the UI to display English text for Romanian users.</violation>
<violation number="3" location="packages/twenty-front/src/locales/ro-RO.po:1590">
P2: Missing Romanian translation for "Background Colors". Empty `msgstr` will cause the UI to display English text for Romanian users.</violation>
</file>
<file name="packages/twenty-front/src/locales/de-DE.po">
<violation number="1" location="packages/twenty-front/src/locales/de-DE.po:1590">
P2: Missing German translation for "Rich Text". The `msgstr` is empty but should contain the German translation (e.g., "Rich-Text" or "Formatierter Text").</violation>
</file>
<file name="packages/twenty-front/src/locales/uk-UA.po">
<violation number="1" location="packages/twenty-front/src/locales/uk-UA.po:1590">
P3: Missing Ukrainian translation for "Rich Text". Users with Ukrainian locale will see English text instead. Consider adding the translation: "Форматований текст".</violation>
</file>
<file name="packages/twenty-front/src/locales/he-IL.po">
<violation number="1" location="packages/twenty-front/src/locales/he-IL.po:1590">
P2: Missing Hebrew translation for "Background Colors". Empty `msgstr` will display untranslated English text to Hebrew users.</violation>
<violation number="2" location="packages/twenty-front/src/locales/he-IL.po:9238">
P2: Missing Hebrew translation for "Text Colors". Empty `msgstr` will display untranslated English text to Hebrew users.</violation>
</file>
<file name="packages/twenty-front/src/locales/pl-PL.po">
<violation number="1" location="packages/twenty-front/src/locales/pl-PL.po:1590">
P2: Missing Polish translation for "Text Colors". The `msgstr` is empty, which will cause users to see the English text. Consider adding the Polish translation: "Kolory tekstu".</violation>
<violation number="2" location="packages/twenty-front/src/locales/pl-PL.po:1590">
P2: Missing Polish translation for "Rich Text". The `msgstr` is empty, which will cause users to see the English text. Consider adding the Polish translation: "Tekst sformatowany".</violation>
<violation number="3" location="packages/twenty-front/src/locales/pl-PL.po:1590">
P2: Missing Polish translation for "Background Colors". The `msgstr` is empty, which will cause users to see the English text. Consider adding the Polish translation: "Kolory tła".</violation>
</file>
<file name="packages/twenty-front/src/locales/nl-NL.po">
<violation number="1" location="packages/twenty-front/src/locales/nl-NL.po:1590">
P2: Missing Dutch translation for "Background Colors". Consider adding `Achtergrondkleuren` as the translation to ensure Dutch users see localized text instead of falling back to English.</violation>
<violation number="2" location="packages/twenty-front/src/locales/nl-NL.po:7952">
P2: Missing Dutch translation for "Rich Text". Consider adding `Opgemaakte tekst` or keeping it as `Rich Text` if that's the preferred terminology in Dutch contexts.</violation>
</file>
Reply to cubic to teach it or ask questions. Re-run a review with @cubic-dev-ai review this PR
|
|
||
| #. js-lingui-id: fq+5a1 | ||
| #: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx | ||
| msgid "Text Colors" |
Contributor
There was a problem hiding this comment.
P2: Missing Turkish translation for "Text Colors". The msgstr is empty, so Turkish users will see the English text instead.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/locales/tr-TR.po, line 9238:
<comment>Missing Turkish translation for "Text Colors". The `msgstr` is empty, so Turkish users will see the English text instead.</comment>
<file context>
@@ -9220,6 +9233,11 @@ msgstr "metin"
+#. js-lingui-id: fq+5a1
+#: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx
+msgid "Text Colors"
+msgstr ""
+
</file context>
|
|
||
| #. js-lingui-id: NP5Nbf | ||
| #: src/modules/command-menu/pages/page-layout/components/CommandMenuPageLayoutWidgetTypeSelect.tsx | ||
| msgid "Rich Text" |
Contributor
There was a problem hiding this comment.
P2: Missing Turkish translation for "Rich Text". The msgstr is empty, so Turkish users will see the English text instead.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/locales/tr-TR.po, line 7952:
<comment>Missing Turkish translation for "Rich Text". The `msgstr` is empty, so Turkish users will see the English text instead.</comment>
<file context>
@@ -7939,6 +7947,11 @@ msgstr "Dönüş Değeri"
+#. js-lingui-id: NP5Nbf
+#: src/modules/command-menu/pages/page-layout/components/CommandMenuPageLayoutWidgetTypeSelect.tsx
+msgid "Rich Text"
+msgstr ""
+
</file context>
| #. js-lingui-id: Hv/jpu | ||
| #: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx | ||
| msgid "Background Colors" | ||
| msgstr "" |
Contributor
There was a problem hiding this comment.
P2: Missing Chinese translation for "Text Colors". This should be translated (e.g., "文本颜色") to maintain consistency with other translated strings in this locale file.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/locales/zh-CN.po, line 1590:
<comment>Missing Chinese translation for "Text Colors". This should be translated (e.g., "文本颜色") to maintain consistency with other translated strings in this locale file.</comment>
<file context>
@@ -1583,6 +1584,11 @@ msgstr "返回"
+#. js-lingui-id: Hv/jpu
+#: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx
+msgid "Background Colors"
+msgstr ""
+
#. js-lingui-id: NgFKo1
</file context>
Suggested change
| msgstr "" | |
| msgstr "文本颜色" |
| #. js-lingui-id: Hv/jpu | ||
| #: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx | ||
| msgid "Background Colors" | ||
| msgstr "" |
Contributor
There was a problem hiding this comment.
P2: Missing Chinese translation for "Rich Text". This should be translated (e.g., "富文本") to maintain consistency with other translated strings in this locale file.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/locales/zh-CN.po, line 1590:
<comment>Missing Chinese translation for "Rich Text". This should be translated (e.g., "富文本") to maintain consistency with other translated strings in this locale file.</comment>
<file context>
@@ -1583,6 +1584,11 @@ msgstr "返回"
+#. js-lingui-id: Hv/jpu
+#: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx
+msgid "Background Colors"
+msgstr ""
+
#. js-lingui-id: NgFKo1
</file context>
Suggested change
| msgstr "" | |
| msgstr "富文本" |
|
|
||
| #. js-lingui-id: NP5Nbf | ||
| #: src/modules/command-menu/pages/page-layout/components/CommandMenuPageLayoutWidgetTypeSelect.tsx | ||
| msgid "Rich Text" |
Contributor
There was a problem hiding this comment.
P2: Missing Spanish translation for "Rich Text". Empty msgstr means users will see untranslated English text.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/locales/es-ES.po, line 7952:
<comment>Missing Spanish translation for "Rich Text". Empty `msgstr` means users will see untranslated English text.</comment>
<file context>
@@ -7939,6 +7947,11 @@ msgstr "Valor de retorno"
+#. js-lingui-id: NP5Nbf
+#: src/modules/command-menu/pages/page-layout/components/CommandMenuPageLayoutWidgetTypeSelect.tsx
+msgid "Rich Text"
+msgstr ""
+
</file context>
| #. js-lingui-id: Hv/jpu | ||
| #: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx | ||
| msgid "Background Colors" | ||
| msgstr "" |
Contributor
There was a problem hiding this comment.
P2: Missing Polish translation for "Text Colors". The msgstr is empty, which will cause users to see the English text. Consider adding the Polish translation: "Kolory tekstu".
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/locales/pl-PL.po, line 1590:
<comment>Missing Polish translation for "Text Colors". The `msgstr` is empty, which will cause users to see the English text. Consider adding the Polish translation: "Kolory tekstu".</comment>
<file context>
@@ -1583,6 +1584,11 @@ msgstr "Wstecz"
+#. js-lingui-id: Hv/jpu
+#: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx
+msgid "Background Colors"
+msgstr ""
+
#. js-lingui-id: NgFKo1
</file context>
Suggested change
| msgstr "" | |
| msgstr "Kolory tekstu" |
| #. js-lingui-id: Hv/jpu | ||
| #: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx | ||
| msgid "Background Colors" | ||
| msgstr "" |
Contributor
There was a problem hiding this comment.
P2: Missing Polish translation for "Rich Text". The msgstr is empty, which will cause users to see the English text. Consider adding the Polish translation: "Tekst sformatowany".
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/locales/pl-PL.po, line 1590:
<comment>Missing Polish translation for "Rich Text". The `msgstr` is empty, which will cause users to see the English text. Consider adding the Polish translation: "Tekst sformatowany".</comment>
<file context>
@@ -1583,6 +1584,11 @@ msgstr "Wstecz"
+#. js-lingui-id: Hv/jpu
+#: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx
+msgid "Background Colors"
+msgstr ""
+
#. js-lingui-id: NgFKo1
</file context>
Suggested change
| msgstr "" | |
| msgstr "Tekst sformatowany" |
| #. js-lingui-id: Hv/jpu | ||
| #: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx | ||
| msgid "Background Colors" | ||
| msgstr "" |
Contributor
There was a problem hiding this comment.
P2: Missing Polish translation for "Background Colors". The msgstr is empty, which will cause users to see the English text. Consider adding the Polish translation: "Kolory tła".
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/locales/pl-PL.po, line 1590:
<comment>Missing Polish translation for "Background Colors". The `msgstr` is empty, which will cause users to see the English text. Consider adding the Polish translation: "Kolory tła".</comment>
<file context>
@@ -1583,6 +1584,11 @@ msgstr "Wstecz"
+#. js-lingui-id: Hv/jpu
+#: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx
+msgid "Background Colors"
+msgstr ""
+
#. js-lingui-id: NgFKo1
</file context>
Suggested change
| msgstr "" | |
| msgstr "Kolory tła" |
|
|
||
| #. js-lingui-id: NP5Nbf | ||
| #: src/modules/command-menu/pages/page-layout/components/CommandMenuPageLayoutWidgetTypeSelect.tsx | ||
| msgid "Rich Text" |
Contributor
There was a problem hiding this comment.
P2: Missing Dutch translation for "Rich Text". Consider adding Opgemaakte tekst or keeping it as Rich Text if that's the preferred terminology in Dutch contexts.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/locales/nl-NL.po, line 7952:
<comment>Missing Dutch translation for "Rich Text". Consider adding `Opgemaakte tekst` or keeping it as `Rich Text` if that's the preferred terminology in Dutch contexts.</comment>
<file context>
@@ -7939,6 +7947,11 @@ msgstr "Returnwaarde"
+#. js-lingui-id: NP5Nbf
+#: src/modules/command-menu/pages/page-layout/components/CommandMenuPageLayoutWidgetTypeSelect.tsx
+msgid "Rich Text"
+msgstr ""
+
</file context>
| #. js-lingui-id: Hv/jpu | ||
| #: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx | ||
| msgid "Background Colors" | ||
| msgstr "" |
Contributor
There was a problem hiding this comment.
P2: Missing Dutch translation for "Background Colors". Consider adding Achtergrondkleuren as the translation to ensure Dutch users see localized text instead of falling back to English.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/twenty-front/src/locales/nl-NL.po, line 1590:
<comment>Missing Dutch translation for "Background Colors". Consider adding `Achtergrondkleuren` as the translation to ensure Dutch users see localized text instead of falling back to English.</comment>
<file context>
@@ -1583,6 +1584,11 @@ msgstr "Terug"
+#. js-lingui-id: Hv/jpu
+#: src/modules/page-layout/widgets/standalone-rich-text/components/DashboardColorSelectionMenu.tsx
+msgid "Background Colors"
+msgstr ""
+
#. js-lingui-id: NgFKo1
</file context>
Suggested change
| msgstr "" | |
| msgstr "Achtergrondkleuren" |
Contributor
Author
LogDetails |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Created by Github action