移动应用
harmony-arkts-code-review
更新于 2026-09-01
HarmonyOS ArkTS · 代码评审规则
Code-review rules for HarmonyOS ArkTS: risk-first reading, reproducible verification and bounded diffs.
- 技术栈
- HarmonyOS ArkTS
- 主题
- 代码评审
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Read the diff risk-first: data changes, auth changes, then everything else
- ✓ Ask for reproducible verification instead of "looks good"
- ✓ Keep review requests under a few hundred lines where possible
✕ 常见反模式
- ✕ Style debates that the formatter should settle
- ✕ Approving migrations without a rollback plan
- ✕ Rubber-stamping config changes that touch production
◎ 交付前验证
- ◎ Verified on both target platforms, not just the emulator
- ◎ Cold-start time and frame budget re-measured on a mid-range device
- ◎ Accessibility labels present on interactive elements
同分类条目
26 篇移动应用
Flutter 工程规则
Flutter rules: adapter-separated platform code and rebuild-scope discipline
移动应用
React Native 工程规则
React Native rules: native module boundaries and release-mode measurement
移动应用
Android Compose 工程规则
Jetpack Compose rules: stateless composables and stable remember keys
移动应用
SwiftUI 工程规则
SwiftUI rules: single source of truth state and MainActor UI updates
移动应用
HarmonyOS ArkTS 工程规则
ArkTS rules: declarative state decorators and ability lifecycle handling
移动应用
WeChat Mini Program 工程规则
Mini Program rules: setData payload discipline and package-size budget