Excess property checks vs structural compatibility in Typescript - Quick Revision & Key Differences

Recall & Review

beginner

What are excess property checks in TypeScript?

Excess property checks happen when you assign an object literal to a variable or parameter with a specific type, and TypeScript warns if the object has extra properties not defined in that type.

beginner

Explain structural compatibility in TypeScript.

Structural compatibility means TypeScript compares the shape (properties and types) of two types to decide if one can be assigned to the other, ignoring the names of types.

intermediate

Why does TypeScript allow extra properties when assigning variables but not with object literals?

TypeScript performs excess property checks only on object literals to catch typos or mistakes. When assigning variables, it trusts the variable's type and uses structural compatibility, allowing extra properties.

intermediate

How can you bypass excess property checks when passing object literals?

You can assign the object literal to a variable first, or use a type assertion (like 'as') to tell TypeScript to trust the object shape, bypassing excess property checks.

intermediate

Give an example where excess property checks cause an error but structural compatibility allows assignment.

Example: Passing {a: 1, b: 2, c: 3} directly to a function expecting {a: number, b: number} causes an error due to excess property 'c'. But assigning it to a variable first and then passing it works because of structural compatibility.

What triggers excess property checks in TypeScript?

A Assigning a variable to another variable

B Using type assertions

C Assigning an object literal directly to a typed variable or parameter

D Declaring interfaces

Excess property checks happen only when assigning object literals directly to typed variables or parameters.

What does structural compatibility in TypeScript compare?

A The shape (properties and types) of types

B The runtime values

C The order of properties

D The names of types

Structural compatibility compares the shape, meaning the properties and their types, ignoring names.

Which of these will cause an excess property check error?

A Using a type assertion

B Assigning {x: 1, y: 2, z: 3} to a variable typed {x: number, y: number}

C Assigning a variable with extra properties to a typed variable

D Passing {x: 1, y: 2, z: 3} directly to a function expecting {x: number, y: number}

Assigning an object literal with extra properties directly to a typed variable or parameter triggers excess property checks and causes an error.

How can you avoid excess property check errors when passing extra properties?

A Remove all extra properties

B Assign the object literal to a variable first

C Use a different language

D Ignore TypeScript errors

Assigning the object literal to a variable first bypasses excess property checks due to structural compatibility.

Does TypeScript check excess properties when assigning variables to variables?

A No, it uses structural compatibility

B Only if variables have different names

C Yes, always

D Only in strict mode

TypeScript uses structural compatibility when assigning variables, so excess property checks do not apply.

Explain the difference between excess property checks and structural compatibility in TypeScript.

Think about when TypeScript warns about extra properties and when it allows them.

How can you handle a situation where an object literal has extra properties but you want to assign it to a type without errors?

Consider ways to bypass excess property checks safely.