arkui-api-design

To design ArkUI component APIs consistently, follow OpenHarmony standards for interface definitions, modifier synchronization, resource typing, and JSDoc documentation to ensure adherence to coding guidelines.

Handling deprecations when renaming ArkUI methods requires providing explicit migration paths and JSDoc documentation to guide developers, ensuring consistent API reviews and transitions across OpenHarmony scenarios.

Yes, OpenHarmony API design requires supporting Resource types for ArkUI properties to ensure consistent resource typing across components, alongside documenting undefined or null behavior explicitly.

Document unit constraints and undefined or null behavior in ArkUI APIs by providing explicit JSDoc documentation, ensuring interface definitions meet OpenHarmony API design standards for clarity and consistency.

Yes, you can use this approach to audit existing ArkUI APIs for consistency by acting as a reference to review interface definitions, modifiers, and JSDoc documentation against OpenHarmony coding guidelines.