| Prio | Original string | Translation | — |
|---|---|---|---|
| Lists the editable properties a %1$s exposes: for each one, the property_key that set-component-instance-properties takes, which element and control it maps to, its label, whether it is enabled, and the default value the %1$s itself renders. On a page, find an instance's %1$s via get-post-tree at content.content.block.componentId. | You have to log in to add a translation. | Details | |
|
Lists the editable properties a %1$s exposes: for each one, the property_key that set-component-instance-properties takes, which element and control it maps to, its label, whether it is enabled, and the default value the %1$s itself renders. On a page, find an instance's %1$s via get-post-tree at content.content.block.componentId.
You have to log in to edit this translation.
|
|||
| Get Component Editable Properties | Získat upravitelné vlastnosti komponenty | Details | |
|
Get Component Editable Properties Získat upravitelné vlastnosti komponenty
You have to log in to edit this translation.
|
|||
| First search %2$s for an existing report of this problem, trying a few keyword combinations, not just the exact title (gh CLI: `gh issue list --search`, a GitHub MCP search tool, or `search_url`). If a matching issue exists, ask the user for permission to post `report_markdown` as a comment on it instead of opening a duplicate — a fresh reproduction with a different environment is still valuable, and comment even if the issue is closed (it may be a regression). Otherwise ask the user for permission to file a new issue on the official %1$s bug tracker (%2$s). With their consent, open it yourself using whatever GitHub access you have (gh CLI, a GitHub MCP server), using `title` and `report_markdown` verbatim — or hand the user `new_issue_url` to review and submit themselves. Never post anything without the user's consent, and if they decline, offer to save the report to a local file so they can submit it later. | You have to log in to add a translation. | Details | |
|
First search %2$s for an existing report of this problem, trying a few keyword combinations, not just the exact title (gh CLI: `gh issue list --search`, a GitHub MCP search tool, or `search_url`). If a matching issue exists, ask the user for permission to post `report_markdown` as a comment on it instead of opening a duplicate — a fresh reproduction with a different environment is still valuable, and comment even if the issue is closed (it may be a regression). Otherwise ask the user for permission to file a new issue on the official %1$s bug tracker (%2$s). With their consent, open it yourself using whatever GitHub access you have (gh CLI, a GitHub MCP server), using `title` and `report_markdown` verbatim — or hand the user `new_issue_url` to review and submit themselves. Never post anything without the user's consent, and if they decline, offer to save the report to a local file so they can submit it later.
You have to log in to edit this translation.
|
|||
| A non-empty description is required. | You have to log in to add a translation. | Details | |
| A non-empty title is required. | You have to log in to add a translation. | Details | |
| What to do with the report. | You have to log in to add a translation. | Details | |
| GitHub issue-search URL prefilled with the report title, for checking whether the problem is already reported before filing a new issue. | You have to log in to add a translation. | Details | |
|
GitHub issue-search URL prefilled with the report title, for checking whether the problem is already reported before filing a new issue.
You have to log in to edit this translation.
|
|||
| GitHub new-issue URL prefilled with the title and body (body may be truncated to fit the URL; the full body is in report_markdown). | You have to log in to add a translation. | Details | |
|
GitHub new-issue URL prefilled with the title and body (body may be truncated to fit the URL; the full body is in report_markdown).
You have to log in to edit this translation.
|
|||
| The complete issue body: your description plus the site environment. Use it verbatim as the GitHub issue body. | You have to log in to add a translation. | Details | |
|
The complete issue body: your description plus the site environment. Use it verbatim as the GitHub issue body.
You have to log in to edit this translation.
|
|||
| The issue title to use. | You have to log in to add a translation. | Details | |
| URL of the bug tracker repository. | You have to log in to add a translation. | Details | |
| The official GitHub bug tracker for this builder, as "owner/repo". | You have to log in to add a translation. | Details | |
|
The official GitHub bug tracker for this builder, as "owner/repo".
You have to log in to edit this translation.
|
|||
| The agent product you are running in (e.g. "Claude Code", "Cursor"), if known. | You have to log in to add a translation. | Details | |
|
The agent product you are running in (e.g. "Claude Code", "Cursor"), if known.
You have to log in to edit this translation.
|
|||
| The AI model you are running as (e.g. "claude-sonnet-5"). Pass "unknown" if you genuinely do not know; never guess. | You have to log in to add a translation. | Details | |
|
The AI model you are running as (e.g. "claude-sonnet-5"). Pass "unknown" if you genuinely do not know; never guess.
You have to log in to edit this translation.
|
|||
| Names of the MCP tools involved, e.g. ["html-to-page", "edit-post"]. | You have to log in to add a translation. | Details | |
|
Names of the MCP tools involved, e.g. ["html-to-page", "edit-post"].
You have to log in to edit this translation.
|
|||
Export as • Download Translation Package (Updated 3 weeks ago)