How assignment compatibility is checked in Typescript - Visual Walkthrough

Concept Flow - How assignment compatibility is checked

Start: Have two types

↓

Check if source type fits target type

↓

Are properties compatible?

No→Error: Incompatible

Yes↓

Check method signatures compatibility

↓

Check optional and readonly modifiers

↓

Result: Assignment allowed or not

The process checks if the source type can fit into the target type by comparing properties, methods, and modifiers step-by-step.

Execution Sample

Typescript

interface A { x: number; }
interface B { x: number; y?: string; }
let a: A;
let b: B = { x: 5 };
a = b;

Assign object b of type B to variable a of type A, checking compatibility.

Execution Table

Step	Check	Source Type	Target Type	Result	Action
1	Start assignment	B {x: number, y?: string}	A {x: number}	Pending	Begin compatibility check
2	Check required properties	x: number	x: number	Compatible	Property x matches type number
3	Check extra properties	y?: string (optional)	No y in target	Compatible	Extra optional property allowed
4	Check method signatures	None	None	Compatible	No methods to check
5	Check modifiers	No readonly	No readonly	Compatible	Modifiers compatible
6	Final decision	All checks passed	All checks passed	Compatible	Assignment allowed

💡 All required properties and modifiers are compatible, so assignment is allowed.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 6
a	undefined	compatible with x:number	compatible with optional y	assigned b's value

Key Moments - 3 Insights

Why is it okay to assign B to A even though B has an extra property y?

Because y is optional in B and A does not require it, extra optional properties do not cause incompatibility (see execution_table row 3).

What happens if a required property in A is missing in B?

Assignment fails because required properties must be present and compatible (would fail at execution_table row 2).

Are method signatures checked during assignment compatibility?

Yes, method signatures must be compatible, but in this example there are none, so it passes (see execution_table row 4).

Visual Quiz - 3 Questions

Look at the execution table, at which step do we confirm that extra optional properties do not cause errors?

A Step 2

B Step 5

C Step 3

D Step 6

💡 Hint

Check the row where extra properties like y?: string are discussed.

At which step does the process decide the assignment is allowed?

A Step 6

B Step 5

C Step 4

D Step 3

💡 Hint

Look for the final decision row in the execution_table.

If B lacked property x, what would happen at step 2?

A Compatible, assignment allowed

B Incompatible, assignment error

C Extra properties checked instead

D Modifiers checked first

💡 Hint

Step 2 checks required properties compatibility.

Concept Snapshot

TypeScript assignment compatibility checks if source type fits target type.
It compares required properties, optional properties, methods, and modifiers.
Extra optional properties in source do not cause errors.
All required properties must be present and compatible.
If all checks pass, assignment is allowed.

Full Transcript

In TypeScript, when assigning one variable to another, the compiler checks if the source type can fit into the target type. It starts by comparing required properties to ensure they exist and have compatible types. Then it checks extra properties in the source; optional extras are allowed. Method signatures and modifiers like readonly are also checked. If all these checks pass, the assignment is allowed. For example, assigning an object with properties x and optional y to a variable expecting only x is allowed because y is optional and extra. If a required property is missing, assignment fails. This step-by-step check ensures type safety while allowing flexibility.