feat(i18n): update translations #1612
Closed
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
1 Job Failed: CI / Test and Build / Test and Build failed on "Build application" |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Greptile Overview
Summary
Automated translation update triggered by PR #1607 (Mistral provider addition). Updates documentation translations across 5 languages (Spanish, French, German, Japanese, Chinese) for 6 different documentation sections.
Key Changes
- New guardrails documentation: Complete translations for new guardrails block documentation added in all 5 languages
- Billing model updates: Added new "Billing Model" section to costs documentation explaining subscription + overage pricing and threshold billing
- Chat trigger enhancements: Updated chat trigger docs with detailed file properties table showing URL, name, size, type, uploadedAt, and expiresAt fields
- SDK file upload features: Added comprehensive file upload documentation with browser and Node.js examples for both TypeScript and Python SDKs
- i18n.lock updates: Checksum updates properly track all translated content changes
Critical Issues Found
- Incomplete translations in TypeScript SDK files: All 5 language translations (
typescript.mdx) contain untranslated English text around lines 704-710, specifically the warning callout about API key security and the "React Hook Example" section heading. This affects user experience for non-English speakers viewing these sections.
Confidence Score: 2/5
- This PR should not be merged until translation issues are resolved
- While most translations are accurate and complete, critical sections in all 5 TypeScript SDK translation files contain untranslated English text that would directly impact non-English users. The automated translation process appears to have failed for specific sections, leaving English content in files meant for Spanish, French, German, Japanese, and Chinese audiences. These are documentation changes with no code logic risk, but the incomplete translations defeat the purpose of this PR.
- All TypeScript SDK translation files require immediate attention:
apps/docs/content/docs/{ja,es,zh,fr,de}/sdks/typescript.mdx- each contains untranslated English text around lines 704-710
Important Files Changed
File Analysis
| Filename | Score | Overview |
|---|---|---|
| apps/docs/content/docs/ja/sdks/typescript.mdx | 2/5 | Japanese translation contains untranslated English text for React Hook example section and warning callout |
| apps/docs/content/docs/es/sdks/typescript.mdx | 2/5 | Spanish translation contains untranslated English text for React Hook example section and warning callout |
| apps/docs/content/docs/zh/sdks/typescript.mdx | 2/5 | Chinese translation contains untranslated English text for React Hook example section and warning callout |
| apps/docs/content/docs/fr/sdks/typescript.mdx | 2/5 | French translation contains untranslated English text for React Hook example section and warning callout |
| apps/docs/content/docs/de/sdks/typescript.mdx | 2/5 | German translation contains untranslated English text for React Hook example section and warning callout |
Sequence Diagram
sequenceDiagram
participant GH as GitHub Actions
participant Lingo as Lingo.dev AI
participant Repo as Repository
participant Docs as Documentation Files
Note over GH,Docs: PR #1607 merged to staging
GH->>GH: Detect English doc changes
GH->>Lingo: Request translations
Note right of Lingo: Translate to:<br/>ES, FR, DE, JA, ZH
Lingo->>Lingo: Process English content
Lingo->>Lingo: Generate translations
Note over Lingo: Translation Issue:<br/>Some content not translated
Lingo->>Repo: Return translated files
Repo->>Docs: Update guardrails.mdx (5 langs)
Repo->>Docs: Update costs.mdx (5 langs)
Repo->>Docs: Update typescript.mdx (5 langs)
Repo->>Docs: Update api.mdx (5 langs)
Repo->>Docs: Update chat.mdx (5 langs)
Repo->>Docs: Update python.mdx (5 langs)
Repo->>Docs: Update i18n.lock
GH->>Repo: Create PR #1612
Note over Repo: 31 files changed<br/>3,387 additions<br/>623 deletions
30 files reviewed, 5 comments
Comment on lines
704
to
+710
| <Callout type="warning"> | ||
| ブラウザでSDKを使用する場合、機密性の高いAPIキーを公開しないよう注意してください。バックエンドプロキシや権限が制限された公開APIキーの使用を検討してください。 | ||
| When using the SDK in the browser, be careful not to expose sensitive API keys. Consider using a backend proxy or public API keys with limited permissions. | ||
| </Callout> | ||
| ### Reactフックの例 | ||
| ### React Hook Example | ||
| ワークフロー実行用のカスタムReactフックを作成： | ||
| Create a custom React hook for workflow execution: |
There was a problem hiding this comment.
logic: untranslated English text found in Japanese file - both the warning callout and "React Hook Example" heading remain in English
Suggested change
| <Callout type="warning"> | |
| ブラウザでSDKを使用する場合、機密性の高いAPIキーを公開しないよう注意してください。バックエンドプロキシや権限が制限された公開APIキーの使用を検討してください。 | |
| When using the SDK in the browser, be careful not to expose sensitive API keys. Consider using a backend proxy or public API keys with limited permissions. | |
| </Callout> | |
| ### Reactフックの例 | |
| ### React Hook Example | |
| ワークフロー実行用のカスタムReactフックを作成： | |
| Create a custom React hook for workflow execution: | |
| <Callout type="warning"> | |
| ブラウザでSDKを使用する場合、機密性の高いAPIキーを公開しないよう注意してください。バックエンドプロキシや権限が制限された公開APIキーの使用を検討してください。 | |
| </Callout> | |
| ### Reactフックの例 | |
| ワークフロー実行用のカスタムReactフックを作成： |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/ja/sdks/typescript.mdx
Line: 704:710
Comment:
**logic:** untranslated English text found in Japanese file - both the warning callout and "React Hook Example" heading remain in English
```suggestion
<Callout type="warning">
ブラウザでSDKを使用する場合、機密性の高いAPIキーを公開しないよう注意してください。バックエンドプロキシや権限が制限された公開APIキーの使用を検討してください。
</Callout>
### Reactフックの例
ワークフロー実行用のカスタムReactフックを作成：
```
How can I resolve this? If you propose a fix, please make it concise.
Comment on lines
704
to
+710
| <Callout type="warning"> | ||
| Cuando uses el SDK en el navegador, ten cuidado de no exponer claves API sensibles. Considera usar un proxy de backend o claves API públicas con permisos limitados. | ||
| When using the SDK in the browser, be careful not to expose sensitive API keys. Consider using a backend proxy or public API keys with limited permissions. | ||
| </Callout> | ||
| ### Ejemplo de hook de React | ||
| ### React Hook Example | ||
| Crea un hook personalizado de React para la ejecución de flujos de trabajo: | ||
| Create a custom React hook for workflow execution: |
There was a problem hiding this comment.
logic: untranslated English text found in Spanish file - both the warning callout and "React Hook Example" heading remain in English
Suggested change
| <Callout type="warning"> | |
| Cuando uses el SDK en el navegador, ten cuidado de no exponer claves API sensibles. Considera usar un proxy de backend o claves API públicas con permisos limitados. | |
| When using the SDK in the browser, be careful not to expose sensitive API keys. Consider using a backend proxy or public API keys with limited permissions. | |
| </Callout> | |
| ### Ejemplo de hook de React | |
| ### React Hook Example | |
| Crea un hook personalizado de React para la ejecución de flujos de trabajo: | |
| Create a custom React hook for workflow execution: | |
| <Callout type="warning"> | |
| Al usar el SDK en el navegador, ten cuidado de no exponer claves API sensibles. Considera usar un proxy de backend o claves API públicas con permisos limitados. | |
| </Callout> | |
| ### Ejemplo de React Hook | |
| Crea un hook personalizado de React para la ejecución de flujos de trabajo: |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/es/sdks/typescript.mdx
Line: 704:710
Comment:
**logic:** untranslated English text found in Spanish file - both the warning callout and "React Hook Example" heading remain in English
```suggestion
<Callout type="warning">
Al usar el SDK en el navegador, ten cuidado de no exponer claves API sensibles. Considera usar un proxy de backend o claves API públicas con permisos limitados.
</Callout>
### Ejemplo de React Hook
Crea un hook personalizado de React para la ejecución de flujos de trabajo:
```
How can I resolve this? If you propose a fix, please make it concise.
Comment on lines
704
to
+710
| <Callout type="warning"> | ||
| 在浏览器中使用 SDK 时，请注意不要暴露敏感的 API 密钥。建议使用后端代理或具有有限权限的公共 API 密钥。 | ||
| When using the SDK in the browser, be careful not to expose sensitive API keys. Consider using a backend proxy or public API keys with limited permissions. | ||
| </Callout> | ||
| ### React Hook 示例 | ||
| ### React Hook Example | ||
| 为工作流执行创建自定义 React hook： | ||
| Create a custom React hook for workflow execution: |
There was a problem hiding this comment.
logic: untranslated English text found in Chinese file - both the warning callout and "React Hook Example" heading remain in English
Suggested change
| <Callout type="warning"> | |
| 在浏览器中使用 SDK 时，请注意不要暴露敏感的 API 密钥。建议使用后端代理或具有有限权限的公共 API 密钥。 | |
| When using the SDK in the browser, be careful not to expose sensitive API keys. Consider using a backend proxy or public API keys with limited permissions. | |
| </Callout> | |
| ### React Hook 示例 | |
| ### React Hook Example | |
| 为工作流执行创建自定义 React hook： | |
| Create a custom React hook for workflow execution: | |
| <Callout type="warning"> | |
| 在浏览器中使用SDK时，请注意不要暴露敏感的API密钥。考虑使用后端代理或具有受限权限的公共API密钥。 | |
| </Callout> | |
| ### React Hook 示例 | |
| 创建自定义 React hook 用于工作流执行： |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/zh/sdks/typescript.mdx
Line: 704:710
Comment:
**logic:** untranslated English text found in Chinese file - both the warning callout and "React Hook Example" heading remain in English
```suggestion
<Callout type="warning">
在浏览器中使用SDK时，请注意不要暴露敏感的API密钥。考虑使用后端代理或具有受限权限的公共API密钥。
</Callout>
### React Hook 示例
创建自定义 React hook 用于工作流执行：
```
How can I resolve this? If you propose a fix, please make it concise.
Comment on lines
704
to
+710
| <Callout type="warning"> | ||
| Lors de l'utilisation du SDK dans le navigateur, veillez à ne pas exposer de clés API sensibles. Envisagez d'utiliser un proxy backend ou des clés API publiques avec des permissions limitées. | ||
| When using the SDK in the browser, be careful not to expose sensitive API keys. Consider using a backend proxy or public API keys with limited permissions. | ||
| </Callout> | ||
| ### Exemple de hook React | ||
| ### React Hook Example | ||
| Créer un hook React personnalisé pour l'exécution de workflow : | ||
| Create a custom React hook for workflow execution: |
There was a problem hiding this comment.
logic: untranslated English text found in French file - both the warning callout and "React Hook Example" heading remain in English
Suggested change
| <Callout type="warning"> | |
| Lors de l'utilisation du SDK dans le navigateur, veillez à ne pas exposer de clés API sensibles. Envisagez d'utiliser un proxy backend ou des clés API publiques avec des permissions limitées. | |
| When using the SDK in the browser, be careful not to expose sensitive API keys. Consider using a backend proxy or public API keys with limited permissions. | |
| </Callout> | |
| ### Exemple de hook React | |
| ### React Hook Example | |
| Créer un hook React personnalisé pour l'exécution de workflow : | |
| Create a custom React hook for workflow execution: | |
| <Callout type="warning"> | |
| Lorsque vous utilisez le SDK dans le navigateur, veillez à ne pas exposer de clés API sensibles. Envisagez d'utiliser un proxy backend ou des clés API publiques avec des permissions limitées. | |
| </Callout> | |
| ### Exemple de Hook React | |
| Créez un hook React personnalisé pour l'exécution de workflow : |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/fr/sdks/typescript.mdx
Line: 704:710
Comment:
**logic:** untranslated English text found in French file - both the warning callout and "React Hook Example" heading remain in English
```suggestion
<Callout type="warning">
Lorsque vous utilisez le SDK dans le navigateur, veillez à ne pas exposer de clés API sensibles. Envisagez d'utiliser un proxy backend ou des clés API publiques avec des permissions limitées.
</Callout>
### Exemple de Hook React
Créez un hook React personnalisé pour l'exécution de workflow :
```
How can I resolve this? If you propose a fix, please make it concise.
Comment on lines
704
to
+710
| <Callout type="warning"> | ||
| Bei der Verwendung des SDK im Browser sollten Sie darauf achten, keine sensiblen API-Schlüssel offenzulegen. Erwägen Sie die Verwendung eines Backend-Proxys oder öffentlicher API-Schlüssel mit eingeschränkten Berechtigungen. | ||
| When using the SDK in the browser, be careful not to expose sensitive API keys. Consider using a backend proxy or public API keys with limited permissions. | ||
| </Callout> | ||
| ### React Hook-Beispiel | ||
| ### React Hook Example | ||
| Erstellen eines benutzerdefinierten React-Hooks für die Workflow-Ausführung: | ||
| Create a custom React hook for workflow execution: |
There was a problem hiding this comment.
logic: untranslated English text found in German file - both the warning callout and "React Hook Example" heading remain in English
Suggested change
| <Callout type="warning"> | |
| Bei der Verwendung des SDK im Browser sollten Sie darauf achten, keine sensiblen API-Schlüssel offenzulegen. Erwägen Sie die Verwendung eines Backend-Proxys oder öffentlicher API-Schlüssel mit eingeschränkten Berechtigungen. | |
| When using the SDK in the browser, be careful not to expose sensitive API keys. Consider using a backend proxy or public API keys with limited permissions. | |
| </Callout> | |
| ### React Hook-Beispiel | |
| ### React Hook Example | |
| Erstellen eines benutzerdefinierten React-Hooks für die Workflow-Ausführung: | |
| Create a custom React hook for workflow execution: | |
| <Callout type="warning"> | |
| Achten Sie bei der Verwendung des SDK im Browser darauf, keine sensiblen API-Schlüssel preiszugeben. Erwägen Sie die Verwendung eines Backend-Proxys oder öffentlicher API-Schlüssel mit eingeschränkten Berechtigungen. | |
| </Callout> | |
| ### React-Hook-Beispiel | |
| Erstellen Sie einen benutzerdefinierten React-Hook für die Workflow-Ausführung: |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/de/sdks/typescript.mdx
Line: 704:710
Comment:
**logic:** untranslated English text found in German file - both the warning callout and "React Hook Example" heading remain in English
```suggestion
<Callout type="warning">
Achten Sie bei der Verwendung des SDK im Browser darauf, keine sensiblen API-Schlüssel preiszugeben. Erwägen Sie die Verwendung eines Backend-Proxys oder öffentlicher API-Schlüssel mit eingeschränkten Berechtigungen.
</Callout>
### React-Hook-Beispiel
Erstellen Sie einen benutzerdefinierten React-Hook für die Workflow-Ausführung:
```
How can I resolve this? If you propose a fix, please make it concise.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Automated translation updates triggered by changes to documentation.
This PR was automatically created after content changes were made, updating translations for all supported languages using Lingo.dev AI translation engine.
Original trigger: feat(mistal): added mistral as a provider, updated model prices (#1607)
feat(mistal): added mistral as a provider, updated model prices
remove the ability for a block to reference its own outluts
fixed order of responses for guardrails block
Commit: b10b246
Workflow: https://github.com/simstudioai/sim/actions/runs/18438644873
Type of Change
Testing
This PR includes automated translations for modified English documentation content:
What reviewers should focus on:
Checklist
Screenshots/Videos