feat(i18n): update translations #1490
Conversation
![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
This PR contains automated translation updates for the loop block YAML schema documentation across five languages (Spanish, French, Chinese, Japanese, and German). The changes reflect architectural updates to the loop block configuration that were introduced in the original trigger PR #1488, which deprecated YAML/JSON import/export functionality in favor of a JSON-based copilot system.The primary modifications include making the inputs section optional by removing it from required properties and providing sensible default values (loopType: 'for', iterations: 5, collection: ''). Additionally, a new "direct handle" connection format has been introduced as an alternative to the existing nested loop format, giving users two ways to configure loop connections: the traditional nested loop format and the new direct loop-start-source/loop-end-source format.
These changes integrate with Sim's broader workflow system by making loop blocks more user-friendly and flexible. The optional inputs with defaults reduce configuration complexity for simple use cases, while the dual connection format provides compatibility with both legacy workflows and the new JSON-based architecture. The automated translation system ensures consistency across all supported documentation languages, maintaining technical accuracy while adapting to linguistic conventions.
Important Files Changed
Changed Files
| Filename | Score | Overview |
|---|---|---|
| apps/docs/content/docs/zh/yaml/blocks/loop.mdx | 4/5 | Chinese translation update making inputs optional with defaults and adding direct handle connection format |
| apps/docs/content/docs/ja/yaml/blocks/loop.mdx | 4/5 | Japanese translation update reflecting loop block schema flexibility improvements |
| apps/docs/content/docs/de/yaml/blocks/loop.mdx | 4/5 | German translation update with optional inputs and dual connection format support |
| apps/docs/content/docs/es/yaml/blocks/loop.mdx | 4/5 | Spanish translation update introducing direct handle format and default values |
| apps/docs/content/docs/fr/yaml/blocks/loop.mdx | 4/5 | French translation update aligning with JSON-based copilot conversion |
Confidence score: 4/5
- This PR is safe to merge with minimal risk as it contains automated documentation translations
- Score reflects that translations appear accurate and maintain technical consistency across languages
- Pay attention to verifying that code blocks, YAML structures, and technical terms are properly preserved in all languages
Sequence Diagram
sequenceDiagram
5 files reviewed, 10 comments
| type: string | string[] | ||
| description: Target block ID to execute inside the loop (direct format) | ||
| loop-end-source: | ||
| type: string | string[] | ||
| description: Target block ID for loop completion (direct format, optional) |
There was a problem hiding this comment.
syntax: Type definition shows string | string[] but this union type syntax may not be valid in standard YAML schema notation
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/zh/yaml/blocks/loop.mdx
Line: 62:66
Comment:
syntax: Type definition shows `string | string[]` but this union type syntax may not be valid in standard YAML schema notation
How can I resolve this? If you propose a fix, please make it concise.| loop-start-source: | ||
| type: string | string[] | ||
| description: Target block ID to execute inside the loop (direct format) | ||
| loop-end-source: | ||
| type: string | string[] | ||
| description: Target block ID for loop completion (direct format, optional) |
There was a problem hiding this comment.
style: The type definition 'string | string[]' uses TypeScript union syntax but this is YAML documentation. Consider using YAML-appropriate syntax or clarifying this is for reference only.
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/de/yaml/blocks/loop.mdx
Line: 61:66
Comment:
style: The type definition 'string | string[]' uses TypeScript union syntax but this is YAML documentation. Consider using YAML-appropriate syntax or clarifying this is for reference only.
How can I resolve this? If you propose a fix, please make it concise.| Sie können den Abschnitt `inputs` vollständig weglassen, dann werden Standardwerte angewendet: | ||
|
|
||
| ```yaml | ||
| simple-loop: | ||
| type: loop | ||
| name: "Simple Loop" | ||
| # No inputs section - defaults to loopType: 'for', iterations: 5 |
There was a problem hiding this comment.
syntax: The comment '# No inputs section - defaults to loopType: 'for', iterations: 5' is in English within German documentation. Should be translated for consistency.
| Sie können den Abschnitt `inputs` vollständig weglassen, dann werden Standardwerte angewendet: | |
| ```yaml | |
| simple-loop: | |
| type: loop | |
| name: "Simple Loop" | |
| # No inputs section - defaults to loopType: 'for', iterations: 5 | |
| Sie können den Abschnitt `inputs` vollständig weglassen, dann werden Standardwerte angewendet: | |
| ```yaml | |
| simple-loop: | |
| type: loop | |
| name: "Simple Loop" | |
| # Kein inputs-Abschnitt - Standardwerte: loopType: 'for', iterations: 5 |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/de/yaml/blocks/loop.mdx
Line: 302:308
Comment:
syntax: The comment '# No inputs section - defaults to loopType: 'for', iterations: 5' is in English within German documentation. Should be translated for consistency.
```suggestion
Sie können den Abschnitt `inputs` vollständig weglassen, dann werden Standardwerte angewendet:
```yaml
simple-loop:
type: loop
name: "Simple Loop"
# Kein inputs-Abschnitt - Standardwerte: loopType: 'for', iterations: 5
```
How can I resolve this? If you propose a fix, please make it concise.| required: | ||
| - loop | ||
| properties: | ||
| # Nested format (recommended) |
There was a problem hiding this comment.
style: Consider using Spanish technical terminology - 'Formato anidado (recomendado)' instead of 'Nested format (recommended)' for consistency
| # Nested format (recommended) | |
| # Formato anidado (recomendado) |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/es/yaml/blocks/loop.mdx
Line: 50:50
Comment:
style: Consider using Spanish technical terminology - 'Formato anidado (recomendado)' instead of 'Nested format (recommended)' for consistency
```suggestion
# Formato anidado (recomendado)
```
How can I resolve this? If you propose a fix, please make it concise.| end: | ||
| type: string | ||
| description: Target block ID for loop completion (optional) | ||
| # Direct handle format (alternative) |
There was a problem hiding this comment.
style: Consider translating 'Direct handle format (alternative)' to maintain language consistency throughout the document
| # Direct handle format (alternative) | |
| # Formato de manejador directo (alternativo) |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/es/yaml/blocks/loop.mdx
Line: 60:60
Comment:
style: Consider translating 'Direct handle format (alternative)' to maintain language consistency throughout the document
```suggestion
# Formato de manejador directo (alternativo)
```
How can I resolve this? If you propose a fix, please make it concise.| error: | ||
| type: string | ||
| description: Target block ID for error handling | ||
| note: Use either the nested 'loop' format OR the direct 'loop-start-source' format, not both |
There was a problem hiding this comment.
style: The note should be translated to Spanish: 'nota: Usa el formato anidado 'loop' O el formato directo 'loop-start-source', no ambos'
| note: Use either the nested 'loop' format OR the direct 'loop-start-source' format, not both | |
| nota: Usa el formato anidado 'loop' O el formato directo 'loop-start-source', no ambos |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/es/yaml/blocks/loop.mdx
Line: 70:70
Comment:
style: The note should be translated to Spanish: 'nota: Usa el formato anidado 'loop' O el formato directo 'loop-start-source', no ambos'
```suggestion
nota: Usa el formato anidado 'loop' O el formato directo 'loop-start-source', no ambos
```
How can I resolve this? If you propose a fix, please make it concise.| loop-start-source: process-item # Direct handle format | ||
| loop-end-source: final-results # Direct handle format |
There was a problem hiding this comment.
style: Comments should be in Spanish: '# Formato de manejador directo' instead of '# Direct handle format'
| loop-start-source: process-item # Direct handle format | |
| loop-end-source: final-results # Direct handle format | |
| loop-start-source: process-item # Formato de manejador directo | |
| loop-end-source: final-results # Formato de manejador directo |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/es/yaml/blocks/loop.mdx
Line: 285:286
Comment:
style: Comments should be in Spanish: '# Formato de manejador directo' instead of '# Direct handle format'
```suggestion
loop-start-source: process-item # Formato de manejador directo
loop-end-source: final-results # Formato de manejador directo
```
How can I resolve this? If you propose a fix, please make it concise.| simple-loop: | ||
| type: loop | ||
| name: "Simple Loop" | ||
| # No inputs section - defaults to loopType: 'for', iterations: 5 |
There was a problem hiding this comment.
style: Translate the comment to Spanish: '# Sin sección inputs - por defecto loopType: 'for', iterations: 5'
| # No inputs section - defaults to loopType: 'for', iterations: 5 | |
| # Sin sección inputs - por defecto loopType: 'for', iterations: 5 |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/es/yaml/blocks/loop.mdx
Line: 308:308
Comment:
style: Translate the comment to Spanish: '# Sin sección inputs - por defecto loopType: 'for', iterations: 5'
```suggestion
# Sin sección inputs - por defecto loopType: 'for', iterations: 5
```
How can I resolve this? If you propose a fix, please make it concise.| Les blocs Loop utilisent un format de connexion spécial avec une section `loop` : | ||
| Les blocs de boucle prennent en charge deux formats de connexion : | ||
|
|
||
| ### Format de gestion directe (alternative) |
There was a problem hiding this comment.
style: Missing section title - should be 'Format imbriqué (recommandé)' before the alternative format
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/fr/yaml/blocks/loop.mdx
Line: 77:77
Comment:
style: Missing section title - should be 'Format imbriqué (recommandé)' before the alternative format
How can I resolve this? If you propose a fix, please make it concise.| simple-loop: | ||
| type: loop | ||
| name: "Simple Loop" | ||
| # No inputs section - defaults to loopType: 'for', iterations: 5 |
There was a problem hiding this comment.
style: Comment should be translated to French: '# Aucune section inputs - utilise par défaut loopType: 'for', iterations: 5'
| # No inputs section - defaults to loopType: 'for', iterations: 5 | |
| # Aucune section inputs - utilise par défaut loopType: 'for', iterations: 5 |
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/docs/content/docs/fr/yaml/blocks/loop.mdx
Line: 308:308
Comment:
style: Comment should be translated to French: '# Aucune section inputs - utilise par défaut loopType: 'for', iterations: 5'
```suggestion
# Aucune section inputs - utilise par défaut loopType: 'for', iterations: 5
```
How can I resolve this? If you propose a fix, please make it concise.
waleedlatif1
force-pushed
the
staging
branch
from
f0c20a9 to
010753d
Compare
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: fix(copilot): deprecate yaml, json import/export, deprecate build_workflow tool, convert copilot to json-based (#1488)
Temp commit
Edit workflow self contained
Remove build_workflow
Base bad version
fix lint
Sanitize workflows for copilot
Fixes
Fix import/export buttons
fix autolayout
fix lint
fix training logic to work with json
Add claude sonnet 4.5 to copilot
Lint
Update copilot url
Update default model and fix build errors
Fix tests
Co-authored-by: Vikhyath Mondreti vikhyath@simstudio.ai
Commit: 6a66466
Workflow: https://github.com/simstudioai/sim/actions/runs/18116481951
Type of Change
Testing
This PR includes automated translations for modified English documentation content:
What reviewers should focus on:
Checklist
Screenshots/Videos