arkts-static-spec

ArkTS static semantics rules for type annotations are validated at compile time by referencing the bundled language specification. You can look up rules for types, classes, expressions, and generics to verify allowed constructs and clarify behavior.

To validate an ArkTS language feature in your .ets code, query the bundled specification to confirm whether the construct is allowed. The skill checks against official rules and explicitly flags any unsupported or undocumented features.

ArkTS does not support the exact same type system and syntax as TypeScript due to specific static semantics restrictions. You can compare behavioral differences and address compatibility gaps using the TypeScript-to-ArkTS migration cookbook.

You migrate TypeScript syntax restrictions to ArkTS by consulting the migration cookbook to address compatibility gaps and behavioral differences. This guidance helps clarify compile-time rules and resolve unsupported type constructs during OpenHarmony development.

When the ArkTS specification is silent on a specific code construct, the validation process explicitly flags the feature as not documented. This prevents wrong assumptions and clarifies that the construct lacks official static-semantics guidance.