Your cross‑platform design system may be lying about parity

说明与用途

对跨平台设计系统文档的验证揭示了关于组件可用性的错误声明，促使更新清单并提高准确性。

问题

Documentation claimed component implementations existed on multiple platforms, but many were missing or incorrectly named, leading to false parity claims.

结果

The verification process uncovered missing implementations (e.g., direction‑provider), incorrect API names (e.g., sonner), and fabricated examples (e.g., KinetixChart). Updating the manifest reduced reported component counts but improved documentation accuracy.

工作流

• 1. Extract platform support strings from component manifest JSON.
• 2. For each component and platform, check for a source file matching the platform’s language (Swift, Kotlin, Dart, TypeScript).
• 3. If missing, flag the component as lacking implementation.
• 4. For components with source files, perform a symbol‑level check against the actual package to ensure API names exist.
• 5. Update the manifest to include correct source names or remove unsupported platforms.
• 6. Re‑run checks to confirm all claims are accurate.

证据

Every component page listed its supported platforms.

来源

On its first run it reported that direction-provider had no implementation on any of them.

来源

The rule became: When the checker is wrong, fix the data — not the checker.

来源