i18n(ru): add Russian translations 2026-05-11#5394
Conversation
WalkthroughAdds numerous Russian docs across concepts, features, guides, contributing, and community, plus FAQ/credits/feedback. Updates ru.json translation timestamps only. ChangesRU Documentation Expansion
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Suggested labels
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 30
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
🟠 Major comments (15)
docs/src/content/docs/ru/features/bindings/advanced.mdx-257-257 (1)
257-257:⚠️ Potential issue | 🟠 Major | ⚡ Quick winKeep fenced code blocks identical to source (do not localize comments/text inside code).
Several code blocks here include translated in-code comments (e.g.,
// Приватные поля,// Реализация...,// Внутренний вспомогательный метод). For i18n docs in this repo, code blocks should remain exactly as in the English source to avoid example drift.Based on learnings: “For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files… Code block contents must remain exactly in their original English form across all locale MDX files.”
Also applies to: 279-293, 320-324
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/features/bindings/advanced.mdx` at line 257, Revert translated in-code comments inside the fenced code blocks in the MDX file so they exactly match the English source; specifically replace comments like "// Приватные поля", "// Реализация...", and "// Внутренний вспомогательный метод" with their original English counterparts (e.g., "// Private fields", etc.) and ensure all fenced code blocks remain identical to the English source (also check the other blocks flagged around the later sections).docs/src/content/docs/ru/contributing/index.mdx-79-79 (1)
79-79:⚠️ Potential issue | 🟠 Major | ⚡ Quick winUse
wails3prefix for v3 CLI command examples.This page is v3-focused, but it currently says
wails init -t <framework>. It should usewails3 init -t <framework>.Based on learnings: “When reviewing Wails documentation… Wails v3 CLI commands must use the
wails3prefix.”🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/contributing/index.mdx` at line 79, Update the v3 CLI examples to use the correct `wails3` prefix: replace occurrences of the string `wails init -t <framework>` with `wails3 init -t <framework>` in the doc content (look for the table cell containing "**Template System**" and the phrase `wails init -t <framework>`), ensuring all v3-focused examples and any adjacent CLI references are updated consistently to `wails3`.docs/src/content/docs/ru/contributing/standards.mdx-440-443 (1)
440-443:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix the malformed Go build-tag example in Russian docs.
The Russian documentation file contains an invalid build constraint
//go:build darwinpackage applicationat line 440. This should match the English version: split into a valid//go:build darwinline withpackage applicationon a separate line.Proposed fix
-//go:build darwinpackage application +//go:build darwin + +package application🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/contributing/standards.mdx` around lines 440 - 443, The example Go build-tag is malformed: replace the single line containing the invalid token "//go:build darwinpackage application" with a proper two-line example where the build constraint is "//go:build darwin" on its own line and "package application" on the following line; locate the example by searching for the string "darwinpackage application" or the incorrect "//go:build darwinpackage" and update it to the valid split form.docs/src/content/docs/ru/features/screens/info.mdx-340-343 (1)
340-343:⚠️ Potential issue | 🟠 Major | ⚡ Quick winComplete the
createDPIAwareWindowcode snippet with the full function implementation.The Russian version only shows the function signature and a comment line but is missing the entire function body. The English version provides the complete implementation including base size initialization, DPI scaling calculation, window creation, and position centering. Update the Russian file to include all these details.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/features/screens/info.mdx` around lines 340 - 343, The Russian doc snippet is missing the body of createDPIAwareWindow; replace the placeholder with the full implementation from the English version: implement createDPIAwareWindow(screen *Screen) to set baseWidth/baseHeight, query screen.Scale() (or DPI scaling function used in the repo) to compute scale, compute width/height by multiplying base sizes by scale, create the application.WebviewWindow (using NewWebviewWindow or the repo's constructor) with the computed size and title, center the window on the given Screen by calculating position from screen.Bounds/Size, and return the created *application.WebviewWindow; ensure you use the same function/variable names as in the English implementation (createDPIAwareWindow, Screen, application.WebviewWindow) so the Russian file mirrors the complete behavior.docs/src/content/docs/ru/features/menus/reference.mdx-359-359 (1)
359-359:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftIncomplete section: missing content after header.
The section "Почему это важно:" (Why this is important:) begins at line 359 but has no content following it. The file appears to be truncated or the translation is incomplete. This explanation is critical for users to understand why
menu.Update()must be called after menu state changes, especially on Windows.Please complete this section with the explanation of why calling
menu.Update()is important, or verify that the English source document has this content so it can be translated.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/features/menus/reference.mdx` at line 359, The "Почему это важно:" section is empty and needs a short explanation about requiring menu.Update() after changing menu state; add a sentence or two under the header describing that menu.Update() forces the native menu to be rebuilt/applied so UI changes (checked/disabled/labels) are reflected, and that on Windows changes are not visible until Update() is called (so always call menu.Update() after mutating menu items). Locate the header "Почему это важно:" in the same document and add the translation explaining menu.Update(), referencing the method name menu.Update() and the platform note about Windows behavior.docs/src/content/docs/ru/community/templates.md-24-31 (1)
24-31:⚠️ Potential issue | 🟠 Major | ⚡ Quick winUse
wails3 initfor v3 commandsThe examples currently use
wails init, which is inconsistent with Wails v3 command naming and will mislead new users.Based on learnings: In Wails v3 docs, CLI commands should use the
wails3prefix; if inherited from English source, report upstream and keep locales aligned.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/community/templates.md` around lines 24 - 31, The doc examples and text use the old CLI invocation "wails init"; update all occurrences to the v3 CLI "wails3 init" (e.g., change the example backtick line and any inline references like `wails init -n "Your Project Name" -t ...` to `wails3 init -n "Your Project Name" -t ...`) so the command naming matches Wails v3; keep the existing note about version suffix behavior but ensure its wording still reads correctly after replacing the command name.docs/src/content/docs/ru/features/windows/frameless.mdx-734-769 (1)
734-769:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftKeep fenced code blocks in English (do not localize inline comments)
This JS block contains translated comments (e.g., Russian
// ...). For Wails i18n docs, fenced code content should stay exactly as in the English source to avoid drift and copy/paste breakage.Based on learnings: For Wails documentation i18n PRs, do not translate any text inside fenced code blocks; restore code blocks to English originals.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/features/windows/frameless.mdx` around lines 734 - 769, This code block has inline comments translated to Russian; restore the fenced JS block to the English original so code comments remain unchanged for i18n. Replace the Russian comment lines around the Window handlers (e.g., above document.querySelector('.minimize'), the maximiseBtn block, and the close button) with their English counterparts and ensure function/variable names (Window.Minimise, Window.IsMaximised, Window.Restore, Window.Maximise, Window.Close, maximiseBtn, updateMaximiseButton) and the logic are left intact exactly as in the English source.docs/src/content/docs/ru/contributing/extending-wails.mdx-134-138 (1)
134-138:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftRevert localized comments inside code snippets
The comment inside this fenced Go snippet is localized. Code blocks in translated Wails docs should be kept verbatim from the English source.
Based on learnings: In Wails i18n MDX pages, fenced code content must remain exactly in English.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/contributing/extending-wails.mdx` around lines 134 - 138, The fenced Go snippet in docs/src/content/docs/ru/contributing/extending-wails.mdx contains localized comments and must be reverted to the original English verbatim; update the snippet (the file and snippet that declares const MsgSetOpacity / messageprocessor_window_opacity.go reference) so the comment text is exactly the English version from the canonical docs/source (remove any Russian text inside the code block and restore the original English comment).docs/src/content/docs/ru/contributing/template-system.mdx-134-138 (1)
134-138:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftDo not localize comments inside fenced code blocks
This Go snippet contains translated comment text. For this repo’s i18n docs, code blocks should stay identical to the English source.
Based on learnings: Code block contents in translated Wails MDX files must remain in original English.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/contributing/template-system.mdx` around lines 134 - 138, The fenced Go code block contains a localized (Russian) comment inside the function Validate of the Template type; revert that inline comment back to the original English wording so the code block matches the English source exactly (i.e., replace the Russian comment in func (t *Template) Validate() with the original English comment about checking Node >= 20), ensuring no other parts of the fenced code are modified.docs/src/content/docs/ru/features/bindings/models.mdx-317-335 (1)
317-335:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftKeep code examples verbatim from the English source
This snippet includes localized inline comments in code (e.g.,
// Пустой экземпляр). Please restore fenced code blocks to their original English content.Based on learnings: Translated MDX pages must not translate text inside fenced code blocks.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/features/bindings/models.mdx` around lines 317 - 335, The fenced code block contains localized Russian inline comments; restore the original English comments and text inside the fenced block so examples are verbatim to the English source: replace the Russian comments (e.g., "// Пустой экземпляр", "// С данными", "// Из строки JSON", "// Из объекта") with their original English equivalents in the example that constructs User instances and uses User.createFrom, leaving function/class names (User, createFrom) and code logic unchanged.docs/src/content/docs/ru/features/bindings/services.mdx-547-569 (1)
547-569:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftKeep fenced code examples in English across locales
This and other snippets in the file contain localized inline comments. In this repo’s i18n policy, code blocks should remain verbatim from the English source.
Based on learnings: Wails i18n MDX docs should not translate any text inside fenced code blocks.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/features/bindings/services.mdx` around lines 547 - 569, The fenced code example for TestUserService_GetUser contains localized (Russian) inline comments; replace all non-code comments and inline texts inside that fenced block with the original English comments so the code block remains verbatim with the English source (e.g., change "Создать мок базы данных", "Установить ожидания", "Создать сервис", "Тестирование" back to "Create mock DB", "Set expectations", "Create service", "Test" respectively) and keep the code and identifiers (TestUserService_GetUser, NewUserService, service.GetUser, sqlmock usage) unchanged.docs/src/content/docs/ru/contributing/template-system.mdx-159-160 (1)
159-160:⚠️ Potential issue | 🟠 Major | ⚡ Quick winCLI command uses invalid dash character
Line 159 uses
–help(en dash) instead of--help. The command will fail when copied.Suggested fix
-2. Выполните `go generate ./v3/...` **или** просто `go run ./v3/cmd/wails3 –help`; +2. Выполните `go generate ./v3/...` **или** просто `go run ./v3/cmd/wails3 --help`;🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/contributing/template-system.mdx` around lines 159 - 160, The CLI example uses an en dash in the help flag; update the command string "go run ./v3/cmd/wails3 –help" to use a normal double hyphen "--help" so it reads "go run ./v3/cmd/wails3 --help" (replace the character in the text that appears as `–help` with `--help`).docs/src/content/docs/ru/getting-started/your-first-app.mdx-234-245 (1)
234-245:⚠️ Potential issue | 🟠 Major | ⚡ Quick win
:::tipblock is malformed due to missing line breakThe admonition starts on the same line as paragraph text, which can break MDX parsing/rendering.
Suggested fix
- Это гарантирует, что имя вашего Go-модуля соответствует соглашениям об именовании модулей Go и облегчает обмен вашим кодом.:::tip[Совет] + Это гарантирует, что имя вашего Go-модуля соответствует соглашениям об именовании модулей Go и облегчает обмен вашим кодом. + + :::tip[Совет]🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/getting-started/your-first-app.mdx` around lines 234 - 245, The admonition ":::tip[Совет]" is placed on the same line as paragraph text which breaks MDX; move the entire ":::tip[Совет]" block to its own lines by inserting a blank line before the ":::tip[Совет]" marker and ensure the closing ":::" is also on its own line (i.e., separate the paragraph that ends with "обмена вашим кодом." from the tip block), so the tip block (starting at ":::tip[Совет]" and ending at ":::") is standalone and properly parsed by MDX.docs/src/content/docs/ru/features/windows/multiple.mdx-376-384 (1)
376-384:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMajor: Broken Go syntax in function definition.
Line 376 has the opening brace and first statement concatenated:
title string) {dialog := app.Window.NewWithOptionsThis is invalid Go syntax. The opening
{should be followed by a newline, not immediately by code.🔧 Fix the function formatting
-func ShowModaldialog(parent *application.WebviewWindow, title string) {dialog := app.Window.NewWithOptions(application.WebviewWindowOptions{ +func ShowModaldialog(parent *application.WebviewWindow, title string) { + dialog := app.Window.NewWithOptions(application.WebviewWindowOptions{ Title: title,Insert proper line break and indentation after the function opening brace.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/features/windows/multiple.mdx` around lines 376 - 384, The function definition for ShowModaldialog has the opening brace and first statement concatenated making invalid Go syntax; fix by placing the `{` on its own (or followed by a newline) and moving the body onto the next line with proper indentation, e.g. ensure the block starting with dialog := app.Window.NewWithOptions(application.WebviewWindowOptions{...}) and the parent.AttachModal(dialog) call are each on their own lines inside the function, and that the function ends with a closing `}` so ShowModaldialog, parent *application.WebviewWindow, app.Window.NewWithOptions and parent.AttachModal are properly formatted.docs/src/content/docs/ru/concepts/manager-api.mdx-39-266 (1)
39-266:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRevert translated text inside fenced code blocks to the English source.
Lines 39-266 contain multiple Russian-translated comments inside
```goblocks (for example on Line 40, Line 44, Line 66, etc.). In this repo’s i18n policy, code block content must remain exactly as the original English source. Please restore all fenced code blocks verbatim from the EN page.Based on learnings: “For Wails documentation i18n/translation PRs, do not translate any text inside code blocks in MDX files… Code block contents must remain exactly in their original English form.”
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/concepts/manager-api.mdx` around lines 39 - 266, Revert the Russian translations found inside all fenced ```go``` code blocks (examples include blocks containing app.Event.Emit/app.Event.On, app.Window.New/OnCreate, app.Browser.OpenURL, app.Menu.New/Set, app.SystemTray.New, app.Dialog.OpenFile/SaveFile, app.KeyBinding.Add, app.ContextMenu.New, app.Screen.DipToPhysicalPoint, app.Clipboard.SetText, etc.) back to the original English source; locate each ```go``` block in the file and replace its contents with the verbatim English code from the EN page so code block contents match the upstream English text exactly.
🟡 Minor comments (7)
docs/src/content/docs/ru/feedback.mdx-20-20 (1)
20-20:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winUpdate CLI command references to use
wails3prefix in both English and Russian docs.Line 20 in the Russian feedback file references
wails doctor, but this is also present in the English source (docs/src/content/docs/feedback.mdx). Both files should be updated to usewails3 doctorfor consistency with Wails v3 CLI conventions.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/feedback.mdx` at line 20, Replace the outdated CLI invocation "wails doctor" with "wails3 doctor" in the Russian feedback MDX (the occurrence noted in the diff) and mirror the same change in the English feedback source so both locales use the Wails v3 CLI prefix; ensure the replacement is done inside the inline code/CLI references and update any nearby CLI examples in the same files to the "wails3" prefix for consistency.docs/src/content/docs/ru/contributing/index.mdx-94-94 (1)
94-94:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFix garbled closing sentence text.
Уда的研究appears to be corrupted text in a user-facing line and should be replaced with valid Russian.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/contributing/index.mdx` at line 94, The closing phrase contains corrupted text "Уда的研究" — replace that token with proper Russian, e.g., change the sentence to "Удачи в изучении — добро пожаловать во внутреннее устройство Wails v3!" by updating the string in the docs content (the line containing "Уда的研究 — и добро пожаловать во внутреннее устройство Wails v3!").docs/src/content/docs/ru/features/notifications/overview.mdx-234-243 (1)
234-243:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFix table formatting issues and split into two separate tables.
Lines 236-238 contain formatting errors caused by merging two separate tables. The separator on line 236 is malformed (
|------|-------------------------------------------------|), and the RemoveNotificationCategory row on line 238 has corrupted data ending with|------|------------------------------------------------------------------|.According to the English source, these should be two distinct tables: "Notification Categories" (with RegisterNotificationCategory and RemoveNotificationCategory) and "Managing Notifications" (with RemoveAllPendingNotifications, RemovePendingNotification, etc.).
Proposed fix
### Категории уведомлений | Метод | Описание | -|------|-------------------------------------------------| +|---------------------------------------------------------------|---------------------------------------------------| | `RegisterNotificationCategory(category NotificationCategory)` | Регистрирует повторно используемую категорию уведомлений | -| `RemoveNotificationCategory(categoryID string)` | Удаляет ранее зарегистрированную категорию |------|------------------------------------------------------------------| +| `RemoveNotificationCategory(categoryID string)` | Удаляет ранее зарегистрированную категорию | + +### Управление уведомлениями +| Метод | Описание | +|-------------------------------------------------|------------------------------------------------------------------| | `RemoveAllPendingNotifications()` | Удаляет все ожидающие уведомления (только macOS и Linux) |🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/features/notifications/overview.mdx` around lines 234 - 243, Fix the malformed merged table by splitting it into two separate Markdown tables: one for "Notification Categories" containing rows for RegisterNotificationCategory(category NotificationCategory) and RemoveNotificationCategory(categoryID string), and a second for "Managing Notifications" containing rows for RemoveAllPendingNotifications(), RemovePendingNotification(identifier string), RemoveAllDeliveredNotifications(), RemoveDeliveredNotification(identifier string), and RemoveNotification(identifier string); correct the table separator lines so each table has a proper header row and matching delimiter line (e.g., | Метод | Описание | and |------|-------------------------------------------------|) and remove the stray corrupted separators that merged the tables.docs/src/content/docs/ru/features/bindings/models.mdx-454-454 (1)
454-454:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winHeading contains delimiter artifact
## Продвинутые паттерны---should not include the trailing---.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/features/bindings/models.mdx` at line 454, The heading line "## Продвинутые паттерны---" contains an extra delimiter artifact; edit that line (the heading text "## Продвинутые паттерны---") to remove the trailing '---' so it reads "## Продвинутые паттерны" (ensure no extra whitespace or hyphens remain).docs/src/content/docs/ru/features/windows/frameless.mdx-785-788 (1)
785-788:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winTrailing delimiter artifact in list item
Line 787 ends with
---(...не будут работать---), which looks like a merge/translation artifact and should be removed.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/features/windows/frameless.mdx` around lines 785 - 788, Remove the trailing merge/translation artifact `---` from the list item that currently reads "...не будут работать---"; update the line in the frameless window features list so the item ends cleanly ("...не будут работать") without the extra dashes, ensuring list formatting remains intact in the block containing the three bullet points.docs/src/content/docs/ru/features/browser/integration.mdx-324-326 (1)
324-326:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winMinor: Missing line break between bullet points.
Lines 324-325 have two bullet points concatenated on a single line without a line break:
браузера- УчитываетThis will cause incorrect Markdown rendering where both bullets appear on the same line.
🔧 Fix the list formatting
- - Использует команду `open` для запуска стандартного браузера- Учитывает настройки браузера по умолчанию в Системных настройках + - Использует команду `open` для запуска стандартного браузера + - Учитывает настройки браузера по умолчанию в Системных настройках - Может запрашивать разрешение, если приложение работает в песочницеInsert a proper line break between the two bullet items.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/src/content/docs/ru/features/browser/integration.mdx` around lines 324 - 326, The two bullet points "- Использует команду `open` для запуска стандартного браузера- Учитывает настройки браузера по умолчанию в Системных настройках" are concatenated; split them into two separate list items by inserting a newline between "браузера-" and "Учитывает" so the bullets read as separate lines (identify and edit the combined bullet in the docs src content where the two Russian bullets appear and ensure each starts with "-" on its own line).docs/src/content/docs/ru/features/menus/application.mdx-297-298 (1)
297-298:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFormatting issue: Section heading merged with code block.
Line 297 shows
## Пользовательские менюappearing immediately after the closing of a code block on line 296, without proper spacing. This creates a markdown rendering issue where the heading may not be properly recognized.Add a blank line before the heading:
})
Пользовательские меню
<details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.In
@docs/src/content/docs/ru/features/menus/application.mdxaround lines 297 -
298, Add a single blank line between the closing code fence () and the heading "## Пользовательские меню" so the heading is separated from the preceding code block; locate the closingand ensure there is an empty line
immediately after it before the "## Пользовательские меню" line to fix markdown
rendering.</details> </blockquote></details> </blockquote></details> <details> <summary>🤖 Prompt for all review comments with AI agents</summary>Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.Inline comments:
In@docs/src/content/docs/ru/concepts/architecture.mdx:
- Around line 321-328: The D2 lifecycle diagram is truncated at the "Save:
"Save State" {---" token and not properly closed, breaking MDX rendering; fix
by removing the stray '---', properly close the "Save: "Save State"" node and
its braces, ensure the "Cleanup: "Cleanup Resources"" and "Shutdown:
"Shutdown"" blocks have matching closing braces, and terminate the D2 block so
the following markdown (the questions/Discord link) is separate and renders
correctly.In
@docs/src/content/docs/ru/concepts/bridge.mdx:
- Around line 378-391: The Go code block is malformed because the delimiter
artifact '---' was inserted inside the GetUser return literal and the code fence
wasn't closed; locate the User struct and GetUser function and remove the stray
'---', ensure the GetUser function and the surrounding code block are properly
closed, and add the missing closing backticks (```) after the function so the
MDX code fence is valid and the remaining page content is not swallowed.In
@docs/src/content/docs/ru/concepts/lifecycle.mdx:
- Around line 315-319: The document contains a malformed table fragment inserted
into prose after the closeDatabase() call; remove the stray divider text
("----------|--------------------------------|") and either restore the full
Markdown table with a proper header row and the OS rows (macOS, Windows, Linux)
or convert that fragment into a short prose sentence explaining the platform
behaviors. Locate the corrupted snippet referencing closeDatabase() and the
lines showing "| macOS | Приложение продолжает работать..." and fix the
translation so the table or prose is complete and syntactically valid (balanced
pipes/headers), ensuring the number of code blocks and translated content
matches the source.- Line 368: The file is truncated: a stray closing brace
}appears before the
line "Вопросы о жизненном циkле?" and the database service example code block
begun around line ~356 is missing its closing fence; regenerate or restore the
missing translated content from the English source so all code fences are
balanced (original code block count 27 vs current 11), close the open
triple-backtick "```" for the database service example, and ensure the section
header "Вопросы о жизненном цикле?" and surrounding paragraphs are intact and
follow the restored content.In
@docs/src/content/docs/ru/contributing/architecture/bindings.mdx:
- Around line 107-135: Revert all translated text inside fenced code blocks back
to the original English content so the code block contents exactly match the
English source; specifically restore the directive comments and examples that
use the //wails:inject and //wails:id lines and any inline comment text inside
the triple-backtick blocks (the segments shown in the diff with...),
ensuring no Russian translations remain inside those fenced code blocks.In
@docs/src/content/docs/ru/contributing/getting-started.mdx:
- Around line 68-332: The fenced code blocks have been translated into Russian
but must remain in original English; revert all comments inside triple-backtick
blocks (e.g., the bash block lines currently containing "# Воспроизведите
ошибку, чтобы понять её", "# Внесите свои изменения", and the Go/test examples
and comments like "# Добавьте тесты в файлы *_test.go" and "# Внесите свои
изменения") back to the exact English source text used in the canonical docs;
search for any code fences in this MDX (bash/Go snippets shown in the diff) and
replace the translated comment strings with the original English comment strings
so the code blocks match the English source exactly.In
@docs/src/content/docs/ru/contributing/setup.mdx:
- Around line 84-287: Revert all Russian translations inside code blocks back to
the original English comments and commands: replace the Russian shell comments
and any translated inline text in blocks containing the exact snippets "git
clone https://github.com/YOUR_USERNAME/wails.git", "go build -o ../wails3
./cmd/wails3", "export PATH=$PATH:/path/to/wails", verification commands
including "go version" and "./wails3 init -n mytest -t vanilla", test/coverage
commands like "go test ./... -coverprofile=coverage.out", documentation commands
"npm install" / "npm run dev" / "npm run build", and debug snippets (the .vscode
launch configuration and dlv command) so that all content inside those fenced
code blocks is in English and matches the upstream/source-language code blocks
verbatim.- Around line 15-18: The code block contains Russian comments that must remain
in English; replace the two Russian comment lines "# Скачайте с
https://go.dev/dl/" and "go version # Проверьте установку" with their English
equivalents "# Download from https://go.dev/dl/" and "go version # Verify
installation" so the bash code block stays untranslated across locale MDX files.- Around line 21-25: Replace the Russian comment in the shown code block with
its English equivalent so code blocks remain untranslated: change the comment
string "# Добавьте в профиль вашей оболочки (.bashrc, .zshrc и т.д.)" to "# Add
to your shell profile (.bashrc, .zshrc, etc.)" while leaving the export lines
"export GOPATH=$HOME/go" and "export PATH=$PATH:$GOPATH/bin" unchanged.- Around line 37-41: The code block contains Russian comments; revert them to
English by replacing the comment lines in the bash snippet: change "# Установите
Node.js 20+ и npm" to "# Install Node.js 20+ and npm" and change "node --versionДолжно быть 20+" to "node --version # Should be 20+", keep the "npm
--version" line and the ```bash fence unchanged so the code block remains in
English.
- Around line 47-53: Replace the Russian comments inside the bash code block
that surrounds the commands "xcode-select --install" and "xcode-select -p" with
English comments: change the comment before xcode-select --install to "Install
Xcode Command Line Tools" and the comment before xcode-select -p to "Verify
installation" and update the inline comment after xcode-select -p to "Should
print path"; ensure no other text inside the fenced code block is translated.In
@docs/src/content/docs/ru/features/bindings/best-practices.mdx:
- Around line 18-364: The fenced code blocks contain translated comments and
must be reverted to the original English text; locate the example symbols like
type AppService, FileService, UserService, EmailService, PaymentService,
functions SaveFile/Save/GetByID/Send/Process, and other code blocks (e.g.,
ProcessItems, GetUsers, CachedService, ProcessLargeFile, AuthService) and
restore all inline comments and comment markers inside those fenced code blocks
to the original English phrasing (e.g., "// ❌ Bad: ...", "// ✅ Good: ...", "N
bridge calls", etc.) so the code blocks match the English source exactly.In
@docs/src/content/docs/ru/features/bindings/enums.mdx:
- Line 395: The table row currently has a malformed tail where the separator
token is appended to the row text (|complex64,complex128| Нет |---);
edit the markdown so the row ends cleanly (|complex64,complex128| Нет |) and place the section separator on its own line (---) following the table;
locate the offending text in the enums supported-types table and split them into
two valid markdown lines accordingly.In
@docs/src/content/docs/ru/features/bindings/services.mdx:
- Around line 366-397: The fenced code block in the RegisterUser example is
broken: a stray "go" was inserted inside the User struct literal (around PasswordHash) which corrupts the snippet and rendering. Remove the stray fence token and restore the intended indentation and closing braces so the struct literal finishes with PasswordHash and CreatedAt, then close the function body and the example block; specifically fix inside UserService.RegisterUser around the User struct (PasswordHash, CreatedAt) and the subsequent if err := s.repo.Create(user) block so the example compiles and the closing "" fence
remains only at the end of the snippet.In
@docs/src/content/docs/ru/features/clipboard/basics.mdx:
- Around line 405-409: The "Лучшие практики" section under the heading "### ✅
Рекомендуется" is truncated (ends with "gracefully---"); restore and complete
this section by replacing the incomplete list item with full bullet points
(e.g., check return values, handle errors gracefully, sanitize clipboard input,
confirm user intent) and add the missing "❌ Не рекомендуется" subsection with
typical don'ts (e.g., writing without consent, storing sensitive data) to match
other Wails docs; use the existing heading "### ✅ Рекомендуется" and add a
corresponding "### ❌ Не рекомендуется" subsection, mirroring structure/content
from similar pages in the docs to ensure consistent formatting and localization.In
@docs/src/content/docs/ru/features/dialogs/custom.mdx:
- Around line 379-383: Remove the stray
---after<h2>Login</h2>, close all
open HTML tags in the example (ensure the<div class="login-dialog">has its
closing</div>and any<form>/<input>elements are complete), add the
missing frontend script section that matches the Go example (e.g., submit
handler wiring) and properly close the markdown code fence (```) so the HTML
block is well-formed; verify and restore the full example by comparing with the
English source to ensure the login form structure and script names match the Go
example above.In
@docs/src/content/docs/ru/features/dialogs/file.mdx:
- Line 328: Replace the malformed code-fence terminator string "
---" with a proper fence close followed by the markdown separator: change "---" to a
closing fence "```" on its own line and then put the separator line "---" on the
next line so the code block is properly terminated and the page renders
correctly.In
@docs/src/content/docs/ru/features/dialogs/message.mdx:
- Around line 381-384: Remove the stray '---' from the opening code fence
(changego--- togo), insert the missing Go "Exit Confirmation" example
copied from the English source into that code block, and ensure the code block
is properly closed with ``` before the subsequent paragraph; locate the block
around the "Подтверждение выхода" section in message.mdx and update the fenced
code contents and fences accordingly.In
@docs/src/content/docs/ru/features/dialogs/overview.mdx:
- Line 374: Replace the malformed code fence "
---" with a proper closing fence "" in the MDX file
(docs/src/content/docs/ru/features/dialogs/overview.mdx) so the code block is
properly terminated; locate the line containing the string "```---" and remove
the trailing "---" so only the triple backticks remain.In
@docs/src/content/docs/ru/features/keyboard/shortcuts.mdx:
- Line 307: The fenced code block is broken because the opening fence marker is
appended to the code line; separate thego fence from the code so the block starts on its own line and the code line contains only the snippet if runtime.GOOS == "darwin" {; specifically, move thego to the line above (or
insert a line break before it) so the file contains an openinggo fence followed by the line with if runtime.GOOS == "darwin" { and then the corresponding closinglater in the example.In
@docs/src/content/docs/ru/features/menus/application.mdx:
- Around line 506-508: The file is truncated after the "Рекомендуемая практика"
/ "Есть вопросы?" section and contains an extraneous '---' splitter; restore the
missing tail by comparing with the original English source for the "Linux"
platform-specific notes and the final closing paragraph, remove the stray '---',
and ensure the "Рекомендуемая практика" and "Есть вопросы?" sections end cleanly
(search for the headings "Рекомендуемая практика", "Есть вопросы?" and the
"Linux" subsection in application.mdx to locate the spot), then re-add the
complete translated Linux notes and proper document closing so the file ends
properly.In
@docs/src/content/docs/ru/features/menus/systray.mdx:
- Around line 310-314: The markdown contains a malformed table fragment starting
with the string "}----------|--------|--------|-------|" which breaks the code
block; remove the stray closing brace, ensure the table uses correct Markdown
table syntax (a header row followed immediately by a separator like "| --- | ---
| --- | --- |"), place the separator line directly under the header row (e.g.,
"| OS | Feature A | Feature B | Notes |" then the separator), and verify the
table is not accidentally inside a fenced code block (check surrounding triple
backticks) so the table renders correctly in systray.mdx.- Around line 386-388: The file
docs/src/content/docs/ru/features/menus/systray.mdx is truncated — the
"Troubleshooting" section and the list item beginning with "2. Размер иконки
слишком большой или слишком маленький---" are cut off and contain a stray '---';
restore the missing Troubleshooting content and finalize the section by removing
the trailing '---', completing the list item text, and ensuring the section ends
with a proper conclusion and links (e.g., the existing Discord and examples
links). Locate the "Troubleshooting" heading and the list item starting with "2.
Размер иконки..." and add the remaining troubleshooting steps, any missing
examples or notes, and a clean closing paragraph so the Markdown structure
(headings, lists, and links) is syntactically valid.In
@docs/src/content/docs/ru/features/platform/dock.mdx:
- Around line 23-241: Several fenced Go code blocks contain translated Russian
comments; revert all code block contents back to the original English source so
code and comments remain identical to upstream. Locate the Go snippets around
the examples that construct the dock service (calls like New(),
NewWithOptions(BadgeOptions)), the BadgeOptions struct, and all method examples
(HideAppIcon(), ShowAppIcon(), SetBadge(), SetCustomBadge(), RemoveBadge(),
GetBadge()) and replace the Russian comment lines (e.g., comments describing
creating the service, badge colors, font names/sizes, and action comments) with
their original English comments from the English MDX source.In
@docs/src/content/docs/ru/features/screens/info.mdx:
- Around line 36-343: Every Go code block contains Russian comments and strings;
revert each code block back to the original English source so code remains fully
English. Locate and update the code blocks that include the Screen struct,
centreOnScreen, moveToScreen,
positionTopLeft/positionTopRight/positionBottomRight,
hasMultipleMonitors/getMonitorCount/listMonitors/chooseMonitor,
MultiMonitorManager (NewMultiMonitorManager, CreateWindowOnScreen,
CreateWindowOnEachScreen), ScreenMonitor (NewScreenMonitor, OnScreenChange,
Start, checkScreens) and createDPIAwareWindow and change all inline comments,
struct field comments, function comments, and example fmt.Print/fmt.Printf
strings back to the English originals from the source file while leaving
surrounding prose (non-code) translated.- Around line 16-28: Replace the Russian comments and any Russian string
literals inside the Go code block with their original English versions: change
the comment before app.Screen.GetAll() to "// Get all screens", the fmt.Printf
label string to "Screen: %s (%dx%d)\n", the comment before
app.Screens.GetPrimary() to "// Get primary screen", and the final fmt.Printf
label to "Primary: %s\n"; keep the calls and identifiers (app.Screen.GetAll,
app.Screens.GetPrimary, fmt.Printf, screen.Name, screen.Width, screen.Height,
primary.Name) unchanged.In
@docs/src/content/docs/ru/features/windows/basics.mdx:
- Around line 411-417: The "macOS" TabItem section is truncated and contains a
broken Go code block; restore the complete macOS-specific content by referencing
the English source and replacing the partial snippet inside the TabItem
label="macOS" (thego code block that currently contains only the comment `// Transparent title bar---`) with the full macOS window examples, remove the stray `---`, ensure the Go code block is correctly closed (), and include any
additional macOS-specific text/examples present in the English version so the
section is complete and functional.In
@docs/src/content/docs/ru/features/windows/events.mdx:
- Around line 419-422: The file is truncated inside the Go example: the struct
declaration "type ManagedWindow struct { app *application.Application---" is
incomplete and the code block / MDX section isn’t closed; restore the missing
portion by completing the ManagedWindow definition (add remaining fields and
methods referenced later in the example), close the code block and surrounding
MDX markup, and ensure references to application.Application remain correct;
locate the original complete "Complete Example" in the upstream source (the
Wails examples/docs) and copy the rest of the struct and any following code so
the example compiles and the documentation finishes properly.In
@docs/src/content/docs/ru/features/windows/multiple.mdx:
- Line 605: The MDX code block closing fence is malformed: replace the stray
string "---" (the closing code fence at the end of the example block) with a proper triple backtick "" so the code block closes correctly; locate the
occurrence of "---" in docs/src/content/docs/ru/features/windows/multiple.mdx (the code block closing fence) and change it to just "".In
@docs/src/content/docs/ru/features/windows/options.mdx:
- Around line 421-423: The RGBA example for BackgroundColour uses an incorrect
field name: change the struct literal in BackgroundColour: application.RGBA{R:
0, G: 0, H: 0, A: 255} to use the Blue field (B) instead of H; update the
application.RGBA literal so it reads B: 0 (i.e., R:, G:, B:, A:) to fix the
typo.
Major comments:
In@docs/src/content/docs/ru/community/templates.md:
- Around line 24-31: The doc examples and text use the old CLI invocation "wails
init"; update all occurrences to the v3 CLI "wails3 init" (e.g., change the
example backtick line and any inline references likewails init -n "Your Project Name" -t ...towails3 init -n "Your Project Name" -t ...) so the
command naming matches Wails v3; keep the existing note about version suffix
behavior but ensure its wording still reads correctly after replacing the
command name.In
@docs/src/content/docs/ru/concepts/manager-api.mdx:
- Around line 39-266: Revert the Russian translations found inside all fenced
gocode blocks (examples include blocks containing
app.Event.Emit/app.Event.On, app.Window.New/OnCreate, app.Browser.OpenURL,
app.Menu.New/Set, app.SystemTray.New, app.Dialog.OpenFile/SaveFile,
app.KeyBinding.Add, app.ContextMenu.New, app.Screen.DipToPhysicalPoint,
app.Clipboard.SetText, etc.) back to the original English source; locate each
goblock in the file and replace its contents with the verbatim English
code from the EN page so code block contents match the upstream English text
exactly.In
@docs/src/content/docs/ru/contributing/extending-wails.mdx:
- Around line 134-138: The fenced Go snippet in
docs/src/content/docs/ru/contributing/extending-wails.mdx contains localized
comments and must be reverted to the original English verbatim; update the
snippet (the file and snippet that declares const MsgSetOpacity /
messageprocessor_window_opacity.go reference) so the comment text is exactly the
English version from the canonical docs/source (remove any Russian text inside
the code block and restore the original English comment).In
@docs/src/content/docs/ru/contributing/index.mdx:
- Line 79: Update the v3 CLI examples to use the correct
wails3prefix:
replace occurrences of the stringwails init -t <framework>withwails3 init -t <framework>in the doc content (look for the table cell containing
"Template System" and the phrasewails init -t <framework>), ensuring all
v3-focused examples and any adjacent CLI references are updated consistently to
wails3.In
@docs/src/content/docs/ru/contributing/standards.mdx:
- Around line 440-443: The example Go build-tag is malformed: replace the single
line containing the invalid token "//go:build darwinpackage application" with a
proper two-line example where the build constraint is "//go:build darwin" on its
own line and "package application" on the following line; locate the example by
searching for the string "darwinpackage application" or the incorrect
"//go:build darwinpackage" and update it to the valid split form.In
@docs/src/content/docs/ru/contributing/template-system.mdx:
- Around line 134-138: The fenced Go code block contains a localized (Russian)
comment inside the function Validate of the Template type; revert that inline
comment back to the original English wording so the code block matches the
English source exactly (i.e., replace the Russian comment in func (t *Template)
Validate() with the original English comment about checking Node >= 20),
ensuring no other parts of the fenced code are modified.- Around line 159-160: The CLI example uses an en dash in the help flag; update
the command string "go run ./v3/cmd/wails3 –help" to use a normal double hyphen
"--help" so it reads "go run ./v3/cmd/wails3 --help" (replace the character in
the text that appears as–helpwith--help).In
@docs/src/content/docs/ru/features/bindings/advanced.mdx:
- Line 257: Revert translated in-code comments inside the fenced code blocks in
the MDX file so they exactly match the English source; specifically replace
comments like "// Приватные поля", "// Реализация...", and "// Внутренний
вспомогательный метод" with their original English counterparts (e.g., "//
Private fields", etc.) and ensure all fenced code blocks remain identical to the
English source (also check the other blocks flagged around the later sections).In
@docs/src/content/docs/ru/features/bindings/models.mdx:
- Around line 317-335: The fenced code block contains localized Russian inline
comments; restore the original English comments and text inside the fenced block
so examples are verbatim to the English source: replace the Russian comments
(e.g., "// Пустой экземпляр", "// С данными", "// Из строки JSON", "// Из
объекта") with their original English equivalents in the example that constructs
User instances and uses User.createFrom, leaving function/class names (User,
createFrom) and code logic unchanged.In
@docs/src/content/docs/ru/features/bindings/services.mdx:
- Around line 547-569: The fenced code example for TestUserService_GetUser
contains localized (Russian) inline comments; replace all non-code comments and
inline texts inside that fenced block with the original English comments so the
code block remains verbatim with the English source (e.g., change "Создать мок
базы данных", "Установить ожидания", "Создать сервис", "Тестирование" back to
"Create mock DB", "Set expectations", "Create service", "Test" respectively) and
keep the code and identifiers (TestUserService_GetUser, NewUserService,
service.GetUser, sqlmock usage) unchanged.In
@docs/src/content/docs/ru/features/menus/reference.mdx:
- Line 359: The "Почему это важно:" section is empty and needs a short
explanation about requiring menu.Update() after changing menu state; add a
sentence or two under the header describing that menu.Update() forces the native
menu to be rebuilt/applied so UI changes (checked/disabled/labels) are
reflected, and that on Windows changes are not visible until Update() is called
(so always call menu.Update() after mutating menu items). Locate the header
"Почему это важно:" in the same document and add the translation explaining
menu.Update(), referencing the method name menu.Update() and the platform note
about Windows behavior.In
@docs/src/content/docs/ru/features/screens/info.mdx:
- Around line 340-343: The Russian doc snippet is missing the body of
createDPIAwareWindow; replace the placeholder with the full implementation from
the English version: implement createDPIAwareWindow(screen *Screen) to set
baseWidth/baseHeight, query screen.Scale() (or DPI scaling function used in the
repo) to compute scale, compute width/height by multiplying base sizes by scale,
create the application.WebviewWindow (using NewWebviewWindow or the repo's
constructor) with the computed size and title, center the window on the given
Screen by calculating position from screen.Bounds/Size, and return the created
*application.WebviewWindow; ensure you use the same function/variable names as
in the English implementation (createDPIAwareWindow, Screen,
application.WebviewWindow) so the Russian file mirrors the complete behavior.In
@docs/src/content/docs/ru/features/windows/frameless.mdx:
- Around line 734-769: This code block has inline comments translated to
Russian; restore the fenced JS block to the English original so code comments
remain unchanged for i18n. Replace the Russian comment lines around the Window
handlers (e.g., above document.querySelector('.minimize'), the maximiseBtn
block, and the close button) with their English counterparts and ensure
function/variable names (Window.Minimise, Window.IsMaximised, Window.Restore,
Window.Maximise, Window.Close, maximiseBtn, updateMaximiseButton) and the logic
are left intact exactly as in the English source.In
@docs/src/content/docs/ru/features/windows/multiple.mdx:
- Around line 376-384: The function definition for ShowModaldialog has the
opening brace and first statement concatenated making invalid Go syntax; fix by
placing the{on its own (or followed by a newline) and moving the body onto
the next line with proper indentation, e.g. ensure the block starting with
dialog := app.Window.NewWithOptions(application.WebviewWindowOptions{...}) and
the parent.AttachModal(dialog) call are each on their own lines inside the
function, and that the function ends with a closing}so ShowModaldialog,
parent *application.WebviewWindow, app.Window.NewWithOptions and
parent.AttachModal are properly formatted.In
@docs/src/content/docs/ru/getting-started/your-first-app.mdx:
- Around line 234-245: The admonition ":::tip[Совет]" is placed on the same line
as paragraph text which breaks MDX; move the entire ":::tip[Совет]" block to its
own lines by inserting a blank line before the ":::tip[Совет]" marker and ensure
the closing ":::" is also on its own line (i.e., separate the paragraph that
ends with "обмена вашим кодом." from the tip block), so the tip block (starting
at ":::tip[Совет]" and ending at ":::") is standalone and properly parsed by
MDX.
Minor comments:
In@docs/src/content/docs/ru/contributing/index.mdx:
- Line 94: The closing phrase contains corrupted text "Уда的研究" — replace that
token with proper Russian, e.g., change the sentence to "Удачи в изучении —
добро пожаловать во внутреннее устройство Wails v3!" by updating the string in
the docs content (the line containing "Уда的研究 — и добро пожаловать во внутреннее
устройство Wails v3!").In
@docs/src/content/docs/ru/features/bindings/models.mdx:
- Line 454: The heading line "## Продвинутые паттерны---" contains an extra
delimiter artifact; edit that line (the heading text "## Продвинутые
паттерны---") to remove the trailing '---' so it reads "## Продвинутые паттерны"
(ensure no extra whitespace or hyphens remain).In
@docs/src/content/docs/ru/features/browser/integration.mdx:
- Around line 324-326: The two bullet points "- Использует команду
openдля
запуска стандартного браузера- Учитывает настройки браузера по умолчанию в
Системных настройках" are concatenated; split them into two separate list items
by inserting a newline between "браузера-" and "Учитывает" so the bullets read
as separate lines (identify and edit the combined bullet in the docs src content
where the two Russian bullets appear and ensure each starts with "-" on its own
line).In
@docs/src/content/docs/ru/features/menus/application.mdx:
- Around line 297-298: Add a single blank line between the closing code fence
() and the heading "## Пользовательские меню" so the heading is separated from the preceding code block; locate the closingand ensure there is an
empty line immediately after it before the "## Пользовательские меню" line to
fix markdown rendering.In
@docs/src/content/docs/ru/features/notifications/overview.mdx:
- Around line 234-243: Fix the malformed merged table by splitting it into two
separate Markdown tables: one for "Notification Categories" containing rows for
RegisterNotificationCategory(category NotificationCategory) and
RemoveNotificationCategory(categoryID string), and a second for "Managing
Notifications" containing rows for RemoveAllPendingNotifications(),
RemovePendingNotification(identifier string), RemoveAllDeliveredNotifications(),
RemoveDeliveredNotification(identifier string), and
RemoveNotification(identifier string); correct the table separator lines so each
table has a proper header row and matching delimiter line (e.g., | Метод |
Описание | and |------|-------------------------------------------------|) and
remove the stray corrupted separators that merged the tables.In
@docs/src/content/docs/ru/features/windows/frameless.mdx:
- Around line 785-788: Remove the trailing merge/translation artifact
---from
the list item that currently reads "...не будут работать---"; update the line in
the frameless window features list so the item ends cleanly ("...не будут
работать") without the extra dashes, ensuring list formatting remains intact in
the block containing the three bullet points.In
@docs/src/content/docs/ru/feedback.mdx:
- Line 20: Replace the outdated CLI invocation "wails doctor" with "wails3
doctor" in the Russian feedback MDX (the occurrence noted in the diff) and
mirror the same change in the English feedback source so both locales use the
Wails v3 CLI prefix; ensure the replacement is done inside the inline code/CLI
references and update any nearby CLI examples in the same files to the "wails3"
prefix for consistency.</details> <details> <summary>🪄 Autofix (Beta)</summary> Fix all unresolved CodeRabbit comments on this PR: - [ ] <!-- {"checkboxId": "4b0d0e0a-96d7-4f10-b296-3a18ea78f0b9"} --> Push a commit to this branch (recommended) - [ ] <!-- {"checkboxId": "ff5b1114-7d8c-49e6-8ac1-43f82af23a33"} --> Create a new PR with the fixes </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
| Shutdown: "Shutdown" { | ||
| Cleanup: "Cleanup Resources" { | ||
| shape: rectangle | ||
| } | ||
|
|
||
| Save: "Save State" {--- | ||
|
|
||
| **Вопросы об архитектуре?** Задавайте их в [Discord](https://discord.gg/JDdSxwjhGf) или проверяйте [справочник API](/ru/reference/overview). No newline at end of file |
There was a problem hiding this comment.
Repair truncated D2 block and markdown boundary.
The lifecycle diagram block is cut off (Save: "Save State" {---) and never properly closed. This is a hard content/MDX correctness issue and will likely break rendering.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ru/concepts/architecture.mdx` around lines 321 - 328,
The D2 lifecycle diagram is truncated at the "Save: \"Save State\" {---" token
and not properly closed, breaking MDX rendering; fix by removing the stray
'---', properly close the "Save: \"Save State\"" node and its braces, ensure the
"Cleanup: \"Cleanup Resources\"" and "Shutdown: \"Shutdown\"" blocks have
matching closing braces, and terminate the D2 block so the following markdown
(the questions/Discord link) is separate and renders correctly.
| ```go | ||
| // Go | ||
| type User struct { | ||
| ID int `json:"id"` | ||
| Name string `json:"name"` | ||
| Email string `json:"email"` | ||
| } | ||
|
|
||
| func GetUser(id int) (*User, error) { | ||
| return &User{ | ||
| ID: id, | ||
| Name: "Alice",--- | ||
|
|
||
| **Вопросы о мосте?** Задавайте их в [Discord](https://discord.gg/JDdSxwjhGf) или смотрите [примеры привязок](https://github.com/wailsapp/wails/tree/master/v3/examples/binding). No newline at end of file |
There was a problem hiding this comment.
Malformed Go code block truncates the page tail
Line 389 contains a delimiter artifact (---) inside the Go snippet, and the struct/function/code fence is left incomplete. This likely breaks MDX parsing and swallows/garbles subsequent content.
Suggested fix
func GetUser(id int) (*User, error) {
return &User{
ID: id,
- Name: "Alice",---
+ Name: "Alice",
+ Email: "alice@example.com",
+ }, nil
}-Вопросы о мосте? Задавайте их в Discord или смотрите примеры привязок.
+Вопросы о мосте? Задавайте их в Discord или смотрите примеры привязок.
</details>
<!-- suggestion_start -->
<details>
<summary>📝 Committable suggestion</summary>
> ‼️ **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.
```suggestion
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ru/concepts/bridge.mdx` around lines 378 - 391, The Go
code block is malformed because the delimiter artifact '---' was inserted inside
the GetUser return literal and the code fence wasn't closed; locate the User
struct and GetUser function and remove the stray '---', ensure the GetUser
function and the surrounding code block are properly closed, and add the missing
closing backticks (```) after the function so the MDX code fence is valid and
the remaining page content is not swallowed.
| // Close connections----------|--------------------------------| | ||
| | macOS | Приложение продолжает работать (меню остается видимым) | | ||
| | Windows | Приложение завершает работу | | ||
| | Linux | Приложение завершает работу | | ||
|
|
There was a problem hiding this comment.
Critical file corruption: Malformed table breaks document structure.
Lines 315-319 show a table header row incorrectly inserted into prose text. This appears to be a corruption from incomplete translation where table content was misplaced.
The text reads:
closeDatabase()
},
})----------|--------------------------------|
| macOS | Приложение продолжает работать (меню остается видимым) |
This suggests the source translation is corrupted or incomplete.
This matches the PR description's CRITICAL flag for this file: "suspiciously short translation (ratio: 0.48), code block count mismatch (src=27, tgt=11)."
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ru/concepts/lifecycle.mdx` around lines 315 - 319, The
document contains a malformed table fragment inserted into prose after the
closeDatabase() call; remove the stray divider text
("----------|--------------------------------|") and either restore the full
Markdown table with a proper header row and the OS rows (macOS, Windows, Linux)
or convert that fragment into a short prose sentence explaining the platform
behaviors. Locate the corrupted snippet referencing closeDatabase() and the
lines showing "| macOS | Приложение продолжает работать..." and fix the
translation so the table or prose is complete and syntactically valid (balanced
pipes/headers), ensuring the number of code blocks and translated content
matches the source.
| } | ||
|
|
||
| return nil | ||
| }**Вопросы о жизненном цикле?** Задавайте их в [Discord](https://discord.gg/JDdSxwjhGf) или проверяйте [примеры](https://github.com/wailsapp/wails/tree/master/v3/examples). No newline at end of file |
There was a problem hiding this comment.
Critical file corruption: File appears truncated.
The file ends abruptly at line 368 with a lone closing brace }, immediately followed by unrelated text. The code block starting around line 356 (database service example) is never properly closed with a closing fence (```).
This confirms the PR description's CRITICAL flag: "code block count mismatch (src=27, tgt=11)" — the translation is severely incomplete and missing more than half the expected code blocks.
The file needs to be regenerated or completed from the English source to include all missing content.
This file was flagged as CRITICAL in the PR description with a QA score of 0.450, the lowest in the batch.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ru/concepts/lifecycle.mdx` at line 368, The file is
truncated: a stray closing brace `}` appears before the line "Вопросы о
жизненном циkле?" and the database service example code block begun around line
~356 is missing its closing fence; regenerate or restore the missing translated
content from the English source so all code fences are balanced (original code
block count 27 vs current 11), close the open triple-backtick "```" for the
database service example, and ensure the section header "Вопросы о жизненном
цикле?" and surrounding paragraphs are intact and follow the restored content.
| ``` | ||
| <language><style>:<content> | ||
| ``` | ||
|
|
||
| Где: | ||
| - `<language>` может быть: | ||
| - `*` - И JavaScript, и TypeScript | ||
| - `j` - Только JavaScript | ||
| - `t` - Только TypeScript | ||
|
|
||
| - `<style>` может быть: | ||
| - `*` - И классы, и интерфейсы | ||
| - `c` - Только классы | ||
| - `i` - Только интерфейсы | ||
|
|
||
| Например: | ||
| ```go | ||
| //wails:inject j*:console.log("JavaScript only"); | ||
| //wails:inject t*:console.log("TypeScript only"); | ||
| ``` | ||
|
|
||
| ### Пользовательские ID методов | ||
|
|
||
| По умолчанию методы идентифицируются по ID на основе хеша. Однако вы можете указать пользовательский ID с помощью директивы `//wails:id`: | ||
|
|
||
| ```go | ||
| //wails:id 42 | ||
| func (s *Service) CustomIDMethod() {} | ||
| ``` |
There was a problem hiding this comment.
Code block content must remain in English.
The comments within code blocks have been translated to Russian, but according to established translation guidelines, all content inside fenced code blocks must remain exactly in their original English form. This includes:
- Comments in code (lines 107-109, 123-126, 132-135)
- All other text within the ``` delimiters
Please revert all code block contents to match the English source exactly. Based on learnings, code blocks in translated MDX files should be identical to the English version.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ru/contributing/architecture/bindings.mdx` around lines
107 - 135, Revert all translated text inside fenced code blocks back to the
original English content so the code block contents exactly match the English
source; specifically restore the directive comments and examples that use the
//wails:inject and //wails:id lines and any inline comment text inside the
triple-backtick blocks (the segments shown in the diff with ``` ... ```),
ensuring no Russian translations remain inside those fenced code blocks.
| ```go | ||
| screens := app.Screen.GetAll() | ||
|
|
||
| for _, screen := range screens { | ||
| fmt.Printf("ID: %s\n", screen.ID) | ||
| fmt.Printf("Имя: %s\n", screen.Name) | ||
| fmt.Printf("Размер: %dx%d\n", screen.Width, screen.Height) | ||
| fmt.Printf("Положение: %d,%d\n", screen.X, screen.Y) | ||
| fmt.Printf("Масштаб: %.2f\n", screen.ScaleFactor) | ||
| fmt.Printf("Основной: %v\n", screen.IsPrimary) | ||
| fmt.Println("---") | ||
| } | ||
| ``` | ||
|
|
||
| ### Основной экран | ||
|
|
||
| ```go | ||
| primary := app.Screens.GetPrimary() | ||
|
|
||
| fmt.Printf("Основной экран: %s\n", primary.Name) | ||
| fmt.Printf("Разрешение: %dx%d\n", primary.Width, primary.Height) | ||
| fmt.Printf("Коэффициент масштабирования: %.2f\n", primary.ScaleFactor) | ||
| ``` | ||
|
|
||
| ### Текущий экран | ||
|
|
||
| Получите экран, на котором находится окно: | ||
|
|
||
| ```go | ||
| screen := app.Screens.GetCurrent(window) | ||
|
|
||
| fmt.Printf("Окно находится на: %s\n", screen.Name) | ||
| ``` | ||
|
|
||
| ### Экран по ID | ||
|
|
||
| ```go | ||
| screen := app.Screens.GetByID("screen-id") | ||
| if screen != nil { | ||
| fmt.Printf("Найден экран: %s\n", screen.Name) | ||
| } | ||
| ``` | ||
|
|
||
| ## Свойства экрана | ||
|
|
||
| ### Структура экрана | ||
|
|
||
| ```go | ||
| type Screen struct { | ||
| ID string // Уникальный идентификатор | ||
| Name string // Имя дисплея | ||
| X int // Позиция по X | ||
| Y int // Позиция по Y | ||
| Width int // Ширина в пикселях | ||
| Height int // Высота в пикселях | ||
| ScaleFactor float32 // Масштаб DPI (1.0, 1.5, 2.0 и т.д.) | ||
| IsPrimary bool // Является ли этот экран основным? | ||
| } | ||
| ``` | ||
|
|
||
| ### Физические и логические пиксели | ||
|
|
||
| ```go | ||
| screen := app.Screens.GetPrimary() | ||
|
|
||
| // Логические пиксели (то, что вы используете) | ||
| logicalWidth := screen.Width | ||
| logicalHeight := screen.Height | ||
|
|
||
| // Физические пиксели (фактическое отображение) | ||
| physicalWidth := int(float32(screen.Width) * screen.ScaleFactor) | ||
| physicalHeight := int(float32(screen.Height) * screen.ScaleFactor) | ||
|
|
||
| fmt.Printf("Логические: %dx%d\n", logicalWidth, logicalHeight) | ||
| fmt.Printf("Физические: %dx%d\n", physicalWidth, physicalHeight) | ||
| fmt.Printf("Масштаб: %.2f\n", screen.ScaleFactor) | ||
| ``` | ||
|
|
||
| **Общие коэффициенты масштабирования:** | ||
| - `1.0` - Стандартный DPI (96 DPI) | ||
| - `1.25` - Масштабирование 125% (120 DPI) | ||
| - `1.5` - Масштабирование 150% (144 DPI) | ||
| - `2.0` - Масштабирование 200% (192 DPI) - Retina | ||
| - `3.0` - Масштабирование 300% (288 DPI) - 4K/5K | ||
|
|
||
| ## Позиционирование окон | ||
|
|
||
| ### Центрирование на экране | ||
|
|
||
| ```go | ||
| func centreOnScreen(window *application.WebviewWindow, screen *Screen) { | ||
| windowWidth, windowHeight := window.Size() | ||
|
|
||
| x := screen.X + (screen.Width-windowWidth)/2 | ||
| y := screen.Y + (screen.Height-windowHeight)/2 | ||
|
|
||
| window.SetPosition(x, y) | ||
| } | ||
| ``` | ||
|
|
||
| ### Позиционирование на конкретном экране | ||
|
|
||
| ```go | ||
| func moveToScreen(window *application.WebviewWindow, screenIndex int) { | ||
| screens := app.Screen.GetAll() | ||
|
|
||
| if screenIndex < 0 || screenIndex >= len(screens) { | ||
| return | ||
| } | ||
|
|
||
| screen := screens[screenIndex] | ||
|
|
||
| // Центрирование на целевом экране | ||
| centreOnScreen(window, screen) | ||
| } | ||
| ``` | ||
|
|
||
| ### Позиционирование относительно экрана | ||
|
|
||
| ```go | ||
| // Верхний левый угол | ||
| func positionTopLeft(window *application.WebviewWindow, screen *Screen) { | ||
| window.SetPosition(screen.X+10, screen.Y+10) | ||
| } | ||
|
|
||
| // Верхний правый угол | ||
| func positionTopRight(window *application.WebviewWindow, screen *Screen) { | ||
| windowWidth, _ := window.Size() | ||
| window.SetPosition(screen.X+screen.Width-windowWidth-10, screen.Y+10) | ||
| } | ||
|
|
||
| // Нижний правый угол | ||
| func positionBottomRight(window *application.WebviewWindow, screen *Screen) { | ||
| windowWidth, windowHeight := window.Size() | ||
| window.SetPosition( | ||
| screen.X+screen.Width-windowWidth-10, | ||
| screen.Y+screen.Height-windowHeight-10, | ||
| ) | ||
| } | ||
| ``` | ||
|
|
||
| ## Поддержка нескольких мониторов | ||
|
|
||
| ### Обнаружение нескольких мониторов | ||
|
|
||
| ```go | ||
| func hasMultipleMonitors() bool { | ||
| return len(app.Screen.GetAll()) > 1 | ||
| } | ||
|
|
||
| func getMonitorCount() int { | ||
| return len(app.Screen.GetAll()) | ||
| } | ||
| ``` | ||
|
|
||
| ### Список всех мониторов | ||
|
|
||
| ```go | ||
| func listMonitors() { | ||
| screens := app.Screen.GetAll() | ||
|
|
||
| fmt.Printf("Найдено монитор(ов): %d\n", len(screens)) | ||
|
|
||
| for i, screen := range screens { | ||
| primary := "" | ||
| if screen.IsPrimary { | ||
| primary = " (Основной)" | ||
| } | ||
|
|
||
| fmt.Printf("%d. %s%s\n", i+1, screen.Name, primary) | ||
| fmt.Printf(" Разрешение: %dx%d\n", screen.Width, screen.Height) | ||
| fmt.Printf(" Позиция: %d,%d\n", screen.X, screen.Y) | ||
| fmt.Printf(" Масштаб: %.2fx\n", screen.ScaleFactor) | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ### Выбор монитора | ||
|
|
||
| ```go | ||
| func chooseMonitor() (*Screen, error) { | ||
| screens := app.Screen.GetAll() | ||
|
|
||
| if len(screens) == 1 { | ||
| return screens[0], nil | ||
| } | ||
|
|
||
| // Показать диалог для выбора | ||
| var options []string | ||
| for i, screen := range screens { | ||
| primary := "" | ||
| if screen.IsPrimary { | ||
| primary = " (Основной)" | ||
| } | ||
| options = append(options, | ||
| fmt.Sprintf("%d. %s%s - %dx%d", | ||
| i+1, screen.Name, primary, screen.Width, screen.Height)) | ||
| } | ||
|
|
||
| // Используйте диалог для выбора | ||
| // (Реализация зависит от вашей системы диалогов) | ||
|
|
||
| return screens[0], nil | ||
| } | ||
| ``` | ||
|
|
||
| ## Полные примеры | ||
|
|
||
| ### Менеджер окон для нескольких мониторов | ||
|
|
||
| ```go | ||
| type MultiMonitorManager struct { | ||
| app *application.Application | ||
| windows map[int]*application.WebviewWindow | ||
| } | ||
|
|
||
| func NewMultiMonitorManager(app *application.Application) *MultiMonitorManager { | ||
| return &MultiMonitorManager{ | ||
| app: app, | ||
| windows: make(map[int]*application.WebviewWindow), | ||
| } | ||
| } | ||
|
|
||
| func (m *MultiMonitorManager) CreateWindowOnScreen(screenIndex int) error { | ||
| screens := m.app.Screen.GetAll() | ||
|
|
||
| if screenIndex < 0 || screenIndex >= len(screens) { | ||
| return errors.New("invalid screen index") | ||
| } | ||
|
|
||
| screen := screens[screenIndex] | ||
|
|
||
| // Создание окна | ||
| window := m.app.Window.NewWithOptions(application.WebviewWindowOptions{ | ||
| Title: fmt.Sprintf("Window on %s", screen.Name), | ||
| Width: 800, | ||
| Height: 600, | ||
| }) | ||
|
|
||
| // Центрирование на экране | ||
| x := screen.X + (screen.Width-800)/2 | ||
| y := screen.Y + (screen.Height-600)/2 | ||
| window.SetPosition(x, y) | ||
|
|
||
| window.Show() | ||
|
|
||
| m.windows[screenIndex] = window | ||
| return nil | ||
| } | ||
|
|
||
| func (m *MultiMonitorManager) CreateWindowOnEachScreen() { | ||
| screens := m.app.Screen.GetAll() | ||
|
|
||
| for i := range screens { | ||
| m.CreateWindowOnScreen(i) | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ### Обнаружение изменений экрана | ||
|
|
||
| ```go | ||
| type ScreenMonitor struct { | ||
| app *application.Application | ||
| lastScreens []*Screen | ||
| changeHandler func([]*Screen) | ||
| } | ||
|
|
||
| func NewScreenMonitor(app *application.Application) *ScreenMonitor { | ||
| return &ScreenMonitor{ | ||
| app: app, | ||
| lastScreens: app.Screen.GetAll(), | ||
| } | ||
| } | ||
|
|
||
| func (sm *ScreenMonitor) OnScreenChange(handler func([]*Screen)) { | ||
| sm.changeHandler = handler | ||
| } | ||
|
|
||
| func (sm *ScreenMonitor) Start() { | ||
| ticker := time.NewTicker(2 * time.Second) | ||
|
|
||
| go func() { | ||
| for range ticker.C { | ||
| sm.checkScreens() | ||
| } | ||
| }() | ||
| } | ||
|
|
||
| func (sm *ScreenMonitor) checkScreens() { | ||
| current := sm.app.Screen.GetAll() | ||
|
|
||
| if len(current) != len(sm.lastScreens) { | ||
| sm.lastScreens = current | ||
| if sm.changeHandler != nil { | ||
| sm.changeHandler(current) | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ### DPI-зависимое изменение размера окна | ||
|
|
||
| ```go | ||
| func createDPIAwareWindow(screen *Screen) *application.WebviewWindow { | ||
| // Базовый размер при масштабе 1.0--- | ||
|
|
||
| **Вопросы?** Задавайте их в [Discord](https://discord.gg/JDdSxwjhGf) или смотрите [примеры работы с экранами](https://github.com/wailsapp/wails/tree/master/v3/examples). No newline at end of file |
There was a problem hiding this comment.
Critical: All code blocks throughout the file contain translated comments.
Every Go code block in this file contains Russian comments, which violates the translation guidelines. Code blocks must remain entirely in English, including:
- Inline comments (
// ...) - Struct field comments
- Function documentation
- Console output strings in example code
This affects approximately 20+ code blocks throughout the document.
Action required: Revert all code block content to match the English source file, preserving only the translated prose text between code blocks.
As per coding guidelines, maintaining English code blocks ensures technical accuracy, prevents copy-paste errors for developers, and allows code examples to work identically across all locale versions of the documentation.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ru/features/screens/info.mdx` around lines 36 - 343,
Every Go code block contains Russian comments and strings; revert each code
block back to the original English source so code remains fully English. Locate
and update the code blocks that include the Screen struct, centreOnScreen,
moveToScreen, positionTopLeft/positionTopRight/positionBottomRight,
hasMultipleMonitors/getMonitorCount/listMonitors/chooseMonitor,
MultiMonitorManager (NewMultiMonitorManager, CreateWindowOnScreen,
CreateWindowOnEachScreen), ScreenMonitor (NewScreenMonitor, OnScreenChange,
Start, checkScreens) and createDPIAwareWindow and change all inline comments,
struct field comments, function comments, and example fmt.Print/fmt.Printf
strings back to the English originals from the source file while leaving
surrounding prose (non-code) translated.
| <TabItem label="macOS" icon="apple"> | ||
| **Специфичные для macOS функции:** | ||
|
|
||
| ```go | ||
| // Transparent title bar--- | ||
|
|
||
| **Возникли вопросы?** Задавайте их в [Discord](https://discord.gg/JDdSxwjhGf) или ознакомьтесь с [примерами работы с окнами](https://github.com/wailsapp/wails/tree/master/v3/examples). No newline at end of file |
There was a problem hiding this comment.
Critical: Incomplete macOS section with broken code block.
The macOS-specific features section is truncated:
- Line 414 opens a Go code block
- Line 415 contains only a partial comment
// Transparent title bar---with stray--- - No actual code follows
- The section ends abruptly before completion
This leaves the macOS platform documentation incomplete and provides no usable examples for macOS-specific window features.
🔧 Restoration required
Verify against the English source to restore the complete macOS platform section including:
- Full code examples for macOS window features
- Proper code block closure
- Any additional macOS-specific content that was truncated
Remove the stray --- and complete the section.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ru/features/windows/basics.mdx` around lines 411 - 417,
The "macOS" TabItem section is truncated and contains a broken Go code block;
restore the complete macOS-specific content by referencing the English source
and replacing the partial snippet inside the TabItem label="macOS" (the ```go
code block that currently contains only the comment `// Transparent title
bar---`) with the full macOS window examples, remove the stray `---`, ensure the
Go code block is correctly closed (```), and include any additional
macOS-specific text/examples present in the English version so the section is
complete and functional.
| type ManagedWindow struct { | ||
| app *application.Application--- | ||
|
|
||
| **Вопросы?** Задавайте их в [Discord](https://discord.gg/JDdSxwjhGf) или смотрите [примеры](https://github.com/wailsapp/wails/tree/master/v3/examples). No newline at end of file |
There was a problem hiding this comment.
Critical file corruption: File appears truncated.
The file ends abruptly at line 420 within a code block. The struct field declaration:
type ManagedWindow struct {
app *application.Application---is incomplete (ends with ---), and the code block is never properly closed. This suggests the file translation was cut off before completion.
The abrupt ending indicates missing content that should follow the "Complete Example" section.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ru/features/windows/events.mdx` around lines 419 - 422,
The file is truncated inside the Go example: the struct declaration "type
ManagedWindow struct { app *application.Application---" is incomplete and the
code block / MDX section isn’t closed; restore the missing portion by completing
the ManagedWindow definition (add remaining fields and methods referenced later
in the example), close the code block and surrounding MDX markup, and ensure
references to application.Application remain correct; locate the original
complete "Complete Example" in the upstream source (the Wails examples/docs) and
copy the rest of the struct and any following code so the example compiles and
the documentation finishes properly.
| } | ||
| } | ||
| } | ||
| ```--- |
There was a problem hiding this comment.
Critical: Malformed code fence with stray ---.
Line 605 contains ```--- instead of just ``` to close the code block. This breaks MDX syntax.
🔧 Fix the code fence
-```---
+```🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ru/features/windows/multiple.mdx` at line 605, The MDX
code block closing fence is malformed: replace the stray string "```---" (the
closing code fence at the end of the example block) with a proper triple
backtick "```" so the code block closes correctly; locate the occurrence of
"```---" in docs/src/content/docs/ru/features/windows/multiple.mdx (the code
block closing fence) and change it to just "```".
| ```go | ||
| BackgroundColour: application.RGBA{R: 0, G: 0, H: 0, A: 255}, | ||
| ``` |
There was a problem hiding this comment.
Fix typo in RGBA struct field name.
Line 422 contains a typo in the code example. The field name H should be B for the Blue component in the RGBA color struct.
🐛 Proposed fix
-BackgroundColour: application.RGBA{R: 0, G: 0, H: 0, A: 255},
+BackgroundColour: application.RGBA{R: 0, G: 0, B: 0, A: 255},📝 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.
| ```go | |
| BackgroundColour: application.RGBA{R: 0, G: 0, H: 0, A: 255}, | |
| ``` |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/src/content/docs/ru/features/windows/options.mdx` around lines 421 -
423, The RGBA example for BackgroundColour uses an incorrect field name: change
the struct literal in BackgroundColour: application.RGBA{R: 0, G: 0, H: 0, A:
255} to use the Blue field (B) instead of H; update the application.RGBA literal
so it reads B: 0 (i.e., R:, G:, B:, A:) to fix the typo.
|
Reviewed the translations in this PR (ru — Russian). Spot-checked
No broken MDX syntax or structural issues found. LGTM — ready to merge. Note: Taliesin is an AI agent. CC @leaanthony |
Automated translation run via Wails Doc Translator agent — 2026-05-11.
QA Scores
Files Flagged for Human Review (score < 0.75)
All other flagged files scored 0.650:
concepts/lifecycle.mdx— Score: 0.450 — Suspiciously short translation (ratio 0.48), Code block count mismatch (src=27, tgt=11)features/bindings/methods.mdx— Code block count mismatch (src=29, tgt=23), Import count mismatch (src=9, tgt=7)features/bindings/models.mdx— Code block count mismatch (src=34, tgt=25), Import count mismatch (src=14, tgt=10)features/bindings/services.mdx— Code block count mismatch (src=23, tgt=22), Import count mismatch (src=2, tgt=1)features/events/system.mdx— Code block count mismatch (src=30, tgt=23), Import count mismatch (src=8, tgt=6)features/menus/systray.mdx— Code block count mismatch (src=21, tgt=13), Import count mismatch (src=4, tgt=3)features/windows/multiple.mdx— Code block count mismatch (src=24, tgt=23), Import count mismatch (src=3, tgt=2)guides/events-reference.mdx— Code block count mismatch (src=20, tgt=15), Import count mismatch (src=19, tgt=15)reference/events.mdx— Code block count mismatch (src=35, tgt=33), Import count mismatch (src=22, tgt=21)reference/window.mdx— Code block count mismatch (src=60, tgt=42), Import count mismatch (src=5, tgt=3)Locales: ru
Files: 102 new translations
CC @leaanthony
Summary by CodeRabbit