Type assertions in Typescript - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a type assertion in TypeScript?

A type assertion tells the TypeScript compiler to treat a value as a specific type, overriding its inferred type without changing the runtime value.

beginner

How do you write a type assertion using the as syntax?

You write the value followed by as and the target type, like: value as TargetType.

intermediate

What is the difference between type assertion and type casting?

Type assertion only tells the compiler to treat a value as a certain type without changing the value at runtime, while type casting actually converts the value to a different type at runtime.

intermediate

Can you use angle-bracket syntax for type assertions in TypeScript? When might it be discouraged?

Yes, you can write <TargetType>value for type assertions. It is discouraged in .tsx files (React) because it conflicts with JSX syntax.

intermediate

What happens if you assert a type incorrectly in TypeScript?

The compiler trusts your assertion, so you might get runtime errors if the actual value does not match the asserted type. Type assertions do not perform checks.

Which syntax is correct for asserting a variable value as type string?

A string as value

B value as string

C <string>value as

D value <as> string

The correct syntax is value as string.

What does a type assertion do at runtime?

A Does nothing to the value

B Performs a type check

C Changes the value's type

D Throws an error if types mismatch

Type assertions only affect the compiler, not the runtime value.

Why might you avoid using angle-bracket type assertions in React (.tsx) files?

A They are slower

B They are deprecated

C They conflict with JSX syntax

D They cause runtime errors

Angle-bracket assertions look like JSX tags and cause syntax errors in .tsx files.

If you assert a variable as a wrong type, what is the risk?

A Compiler will fix it automatically

B The variable will change type at runtime

C Code will not compile

D Runtime errors may occur

Incorrect assertions can lead to runtime errors because the compiler trusts your assertion.

Which of these is NOT a valid reason to use type assertions?

A To convert a value's type at runtime

B To work around incomplete type information

C To tell the compiler a value has a more specific type

D To access properties not in the inferred type

Type assertions do not convert types at runtime; they only affect compile-time checking.

Explain what a type assertion is and how it differs from type casting.

Think about what happens during compilation versus runtime.

Describe the two common syntaxes for type assertions in TypeScript and when to prefer one over the other.

Consider React files and JSX syntax.