docs(cndocs): sync outdated translations batch 2026-04-17#1013
docs(cndocs): sync outdated translations batch 2026-04-17#1013sunnylqm wants to merge 3 commits intoproductionfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughThis PR makes documentation-only edits across multiple Chinese docs: updates frontmatter titles and admonitions, rewords and restructures sections, reformats code examples (including Kotlin/Java snippets), replaces external video sources with local assets, and reorganizes platform listings. No runtime code changes. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
cndocs/gesture-responder-system.md (1)
27-28: Polish inline callback signatures by removing trailing commasThese inline examples read cleaner without the trailing
,and are less likely to be interpreted as mandatory syntax in all contexts.Suggested doc tweak
-- `View.props.onStartShouldSetResponder: evt => true,` - 这个 View 是否希望在触摸开始时成为响应者？ -- `View.props.onMoveShouldSetResponder: evt => true,` - 当这个 View 还不是响应者时，每次触摸在其上移动都会调用此函数：这个 View 是否想要“接管”触摸响应？ +- `View.props.onStartShouldSetResponder: evt => true` - 这个 View 是否希望在触摸开始时成为响应者？ +- `View.props.onMoveShouldSetResponder: evt => true` - 当这个 View 还不是响应者时，每次触摸在其上移动都会调用此函数：这个 View 是否想要“接管”触摸响应？ -- `View.props.onStartShouldSetResponderCapture: evt => true,` -- `View.props.onMoveShouldSetResponderCapture: evt => true,` +- `View.props.onStartShouldSetResponderCapture: evt => true` +- `View.props.onMoveShouldSetResponderCapture: evt => true`Also applies to: 61-62
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@cndocs/gesture-responder-system.md` around lines 27 - 28, Remove the trailing commas from the inline callback examples so the signatures read without a trailing ","; update the occurrences for View.props.onStartShouldSetResponder and View.props.onMoveShouldSetResponder (and the similar examples at the other mentioned spots) to use `evt => true` instead of `evt => true,`, ensuring the docs show the cleaner callback signature format.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@cndocs/fabric-native-components-android.md`:
- Line 3: The page title string "Fabric 原生模块：Android" is misleading; change it
to "Fabric 原生组件：Android" so the title matches the body about Fabric Native
Components (ViewManager, codegenNativeComponent, ReactWebViewManager). Update
the YAML/front-matter title value and any top-level heading that repeats "原生模块"
to "原生组件" to keep consistency across the document.
In `@cndocs/legacy/native-components-android.md`:
- Around line 294-310: The snippet uses requireNativeComponent but doesn't
import it; update the import to bring requireNativeComponent from 'react-native'
so RCTMyCustomView can be resolved—modify the top import (where React and
useCallback are imported) to also import requireNativeComponent, then ensure
RCTMyCustomView = requireNativeComponent('RCTMyCustomView') remains unchanged
and MyCustomView continues to use the onChange callback as shown.
In `@cndocs/out-of-tree-platforms.md`:
- Line 26: 将句子中的时间副词改为更准确的完成时表达：把“从 React Native 0.57 开始，你现在可以通过 React Native 的
JavaScript 打包器 Metro 注册你的 React Native 平台”改为“自 React Native 0.57 起已支持通过 Metro
注册自定义平台”，并保留后半句对 `npx react-native bundle` 和 `.example.js` 后缀的说明（确保提到 Metro、`npx
react-native bundle` 和 `.example.js` 以便定位上下文）。
- Line 22:
把“即将到来的重新架构（Fabric）”这一表述改为中性且与事实一致的描述，例如将句子替换为“新的架构（Fabric）旨在让平台维护更容易”或类似措辞；在文件中查找原句“即将到来的重新架构（[Fabric](/blog/2018/06/14/state-of-react-native-2018)）的目标之一，就是让平台维护变得更容易”并用中性表述替换，确保语义不暗示尚未落地。
---
Nitpick comments:
In `@cndocs/gesture-responder-system.md`:
- Around line 27-28: Remove the trailing commas from the inline callback
examples so the signatures read without a trailing ","; update the occurrences
for View.props.onStartShouldSetResponder and View.props.onMoveShouldSetResponder
(and the similar examples at the other mentioned spots) to use `evt => true`
instead of `evt => true,`, ensuring the docs show the cleaner callback signature
format.
🪄 Autofix (Beta)
✅ Autofix completed
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 802c5730-a4ea-4b77-96f4-0b633270dc87
📒 Files selected for processing (11)
cndocs/alertios.mdcndocs/asyncstorage.mdcndocs/fabric-native-components-android.mdcndocs/gesture-responder-system.mdcndocs/legacy/native-components-android.mdcndocs/legacy/native-modules-intro.mdcndocs/out-of-tree-platforms.mdcndocs/strict-typescript-api.mdcndocs/turbo-native-modules-android.mdcndocs/using-a-listview.mdcndocs/using-a-scrollview.md
| --- | ||
| id: fabric-native-components-android | ||
| title: 'Fabric 原生 UI 组件：Android' | ||
| title: 'Fabric 原生模块：Android' |
There was a problem hiding this comment.
页面标题与正文主题不一致。
当前标题写成“原生模块”，但正文全篇是在讲 Fabric Native Components（ViewManager、codegenNativeComponent、ReactWebViewManager）。建议改回“原生组件”，避免读者误解页面范围。
✏️ 建议修改
-title: 'Fabric 原生模块：Android'
+title: 'Fabric 原生组件：Android'📝 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.
| title: 'Fabric 原生模块：Android' | |
| title: 'Fabric 原生组件：Android' |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@cndocs/fabric-native-components-android.md` at line 3, The page title string
"Fabric 原生模块：Android" is misleading; change it to "Fabric 原生组件：Android" so the
title matches the body about Fabric Native Components (ViewManager,
codegenNativeComponent, ReactWebViewManager). Update the YAML/front-matter title
value and any top-level heading that repeats "原生模块" to "原生组件" to keep
consistency across the document.
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Fixes Applied SuccessfullyFixed 3 file(s) based on 4 unresolved review comments. Files modified:
Commit: The changes have been pushed to the Time taken: |
Fixed 3 file(s) based on 4 unresolved review comments. Co-authored-by: CodeRabbit <noreply@coderabbit.ai>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@cndocs/legacy/native-components-android.md`:
- Line 866: 链接片段 `#imageview-example` 与页面上对应的标题 ID 不匹配，导致页内跳转失效；在文档中找到引用该片段的文本（含
`#imageview-example` 的链接）并修复：要么在对应的 “ImageView 示例” 标题上添加显式锚点 ID（例如 将标题改为 `###
ImageView 示例 {`#imageview-example`}` 或等效语法），要么将链接改为匹配现有标题生成的实际片段（例如
`#imageview`），并确保在文档中更新所有对此片段的引用（检查出现 `@ReactProp` 的示例段落附近的标题名称和链接）。
🪄 Autofix (Beta)
✅ Autofix completed
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: ba1c1f4b-00b4-4fa9-aefe-1c1fff77e885
📒 Files selected for processing (3)
cndocs/fabric-native-components-android.mdcndocs/legacy/native-components-android.mdcndocs/out-of-tree-platforms.md
🚧 Files skipped from review as they are similar to previous changes (2)
- cndocs/fabric-native-components-android.md
- cndocs/out-of-tree-platforms.md
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Fixes Applied SuccessfullyFixed 2 file(s) based on 1 unresolved review comment. Files modified:
Commit: The changes have been pushed to the Time taken: |
Fixed 2 file(s) based on 1 unresolved review comment. Co-authored-by: CodeRabbit <noreply@coderabbit.ai>
1 participant
Summary
scripts/sync-translations.shgetting-startedUpdated docs
alertiosasyncstoragefabric-native-components-androidgesture-responder-systemlegacy/native-components-androidlegacy/native-modules-introout-of-tree-platformsstrict-typescript-apiturbo-native-modules-androidusing-a-listviewusing-a-scrollviewNotes
production, so some files remained false positives after manual verificationgetting-startedwas intentionally left unchanged because CN docs should not be rewritten into Expo-first guidanceValidation
docs/*vscndocs/*git diff --statand file-level diffscndocs/*filesSummary by CodeRabbit