Repository navigation
docs(zh-cn): 补上 keybinds 页面缺失的「绑定值」小节 - #58017
Kissshot-2003 wants to merge 0 commit into
Conversation
![opencode-agent[bot]](https://avatars.githubusercontent.com/in/1549082?s=60&v=4){kind=small}
There was a problem hiding this comment.
This looks good to me. The new 绑定值 section matches the English "Binding Values" section in content and position, and the example is identical. I checked that the forms it describes (a comma-separated string, an array, or an object with key/event/preventDefault/fallthrough) match the keybind schema in packages/tui/src/config/keybind.ts. It uses the page's existing term for keybind (快捷键). Docs only, so there was nothing to run.
Public API: unchanged.
Optional, for a later PR rather than this one: other parts of this page also lag behind the English page. The 禁用快捷键 section doesn't mention that false also works besides "none", and the 前导键 section is missing the paragraphs on the default subagent navigation keybinds and leader_timeout.
Related: #57623
d2fe3e0 to
248bfbe
Compare
Issue for this PR
Refs #57623
Type of change
What does this PR do?
The Chinese keybinds page is missing a section the English page has.
The English
keybinds.mdxdocuments## Binding Values: a binding value may be one shortcut, several comma-separated shortcuts, an array, or an object withkey,event,preventDefaultorfallthrough. Thezh-cncopy never got that section, so a Chinese reader has no way to learn from the docs how to configure more than one shortcut for a binding.This PR adds the missing section to
packages/web/src/content/docs/zh-cn/keybinds.mdx, in the same position it occupies in the English page (between## 前导键and## 禁用快捷键).The terminology follows the page's existing choices and the
zh-cnglossary:keybind/shortcutare 快捷键, and since## Disable Keybindis already 禁用快捷键 here,## Binding Valuesis 绑定值. The code block, the config keys and the schema URL are identical to the English page.The reason the section is missing is the frozen locale sync described in #57623:
docs-locale-sync.ymlhas its job disabled withif: false, so the Chinese copy stopped following the English one. I did not touch the workflow, because whether the sync should point at the v1 tree or the v2 tree is a question about which one is canonical, and #57623 already asks it. This PR just fills the specific gap.How did you verify your code works?
packages/web/src/content/docs/keybinds.mdxandpackages/web/src/content/docs/zh-cn/keybinds.mdx, skipping lines inside fenced code blocks.bun run buildfrompackages/web, which is the tree this page belongs to. The build also regenerates the config schema, so it covers the generated-output check as well.Screenshots / recordings
Not a UI change.
Checklist