prefer-type-annotations

Type annotations validate values against defined interfaces at compile time, whereas type assertions bypass static type checking. Using annotations over assertions improves runtime safety and code maintainability by ensuring values conform to defined types.

To replace type assertions for object literals, define explicit interfaces and apply them as type annotations during variable assignment. This enforces compile-time validation instead of using the 'as' keyword to bypass structural checks.

Type assertions are acceptable only when truly needed, provided you include an inline justification documenting the rationale. This ensures safety by explicitly acknowledging that the standard type annotation validation is intentionally bypassed.

Type annotations improve function return safety by explicitly defining the expected return type. This enforces compile-time static type checking, ensuring the function output strictly conforms to the defined interface rather than relying on inferred or asserted types.

Replacing type assertions with type annotations requires explicit type definitions for variable assignments and function returns. While this adds upfront definition effort, it prevents runtime errors by enforcing static type checking during development.