Type compatibility with classes in Typescript

Introduction

Type compatibility helps TypeScript check if one class can be used where another is expected. It makes your code safer and easier to work with.

When you want to use an object of one class where another class type is expected.

When you want to check if two classes can work together without errors.

When you want to assign an instance of a subclass to a variable typed as a superclass.

When you want to ensure your code accepts objects with similar shapes, even if they come from different classes.

Syntax

Typescript

class ClassA {
  propertyA: string;
}

class ClassB {
  propertyA: string;
  propertyB: number;
}

let a: ClassA;
let b: ClassB;

a = b; // Allowed if ClassB has at least the properties of ClassA
// b = a; // Error if ClassA lacks properties of ClassB

TypeScript uses 'structural typing', meaning compatibility depends on the shape (properties) of the classes, not their names.

Extra properties in the source class are okay when assigning to a target with fewer properties.

Examples

Dog has all properties Animal needs, so you can assign a Dog to an Animal variable.

Typescript

class Animal {
  name: string;
}

class Dog {
  name: string;
  breed: string;
}

let animal: Animal;
let dog: Dog = { name: "Buddy", breed: "Beagle" };

animal = dog; // OK: Dog has all Animal properties
// dog = animal; // Error: Animal lacks 'breed'

NamedPoint has extra property 'name', so it can be assigned to Point, but not the other way around.

Typescript

class Point {
  x: number;
  y: number;
}

class NamedPoint {
  x: number;
  y: number;
  name: string;
}

let point: Point = { x: 1, y: 2 };
let namedPoint: NamedPoint = { x: 1, y: 2, name: "A" };

point = namedPoint; // OK
// namedPoint = point; // Error

Sample Program

This shows that an Employee can be used where a Person is expected because it has all Person's properties.

Typescript

class Person {
  name: string;
  constructor(name: string) {
    this.name = name;
  }
}

class Employee {
  name: string;
  employeeId: number;
  constructor(name: string, id: number) {
    this.name = name;
    this.employeeId = id;
  }
}

let person: Person;
let employee = new Employee("Alice", 123);

person = employee; // OK because Employee has 'name'
console.log(person.name); // Prints 'Alice'

// let newEmployee: Employee = person; // Error: Person lacks 'employeeId'

Important Notes

Type compatibility is based on properties, not class names.

Private or protected members affect compatibility differently; only public members are checked structurally.

Be careful when assigning classes with methods; method signatures must also be compatible.

Summary

TypeScript checks if classes have matching properties to decide compatibility.

You can assign an instance of a class with more properties to a variable typed as a class with fewer properties.

Compatibility helps write flexible and safe code by focusing on object shapes.

Practice

1. In TypeScript, when are two classes considered compatible for assignment?

easy

A. When they have the same number of methods

B. Only if they share the same class name

C. When their instances have matching properties and types

D. If they are declared in the same file

Solution

1. Step 1: Understand Type Compatibility

   TypeScript checks if the properties and their types in one class instance match those expected by another class type.

2. Step 2: Check Class Names and Methods

   Class names or method counts do not affect compatibility; only the shape (properties and types) matters.

3. Final Answer:

   When their instances have matching properties and types -> Option C

4. Quick Check:

   Compatibility = matching properties and types [OK]

Hint: Focus on properties and types, not class names [OK]

Common Mistakes:

• Assuming class names must match
• Thinking method count matters
• Believing file location affects compatibility

2. Which of the following is the correct syntax to assign an instance of class B to a variable typed as class A in TypeScript, assuming compatibility?

easy

A. let a: B = A();

B. let a: A = new B();

C. let a = A(new B());

D. let a = new A(B);

Solution

1. Step 1: Review TypeScript Assignment Syntax

   To assign an instance of class B to a variable typed as A, use let a: A = new B(); if B is compatible with A.

2. Step 2: Identify Incorrect Syntax

   Other options misuse constructor calls or type annotations and are invalid.

3. Final Answer:

   let a: A = new B(); -> Option B

4. Quick Check:

   Use let var: Type = new Class(); [OK]

Hint: Use variable: Type = new Class() for assignments [OK]

Common Mistakes:

• Calling classes like functions
• Swapping variable and type names
• Using incorrect constructor syntax

3. Consider the following TypeScript code:

class A { x: number; }
class B { x: number; y: string; }

let a: A = new B();
console.log(a.x);

What will be the output when this code runs?

medium

A. undefined

B. Runtime error

C. The value of x from B instance

D. Compilation error

Solution

1. Step 1: Analyze Class Properties and Assignment

   Class B has properties x and y. Class A has only x. Assigning new B() to a variable typed as A is allowed because B has at least the properties of A.

2. Step 2: Check Output of console.log(a.x)

   The property x exists on the B instance. Since no value is assigned to x, it is undefined, so console.log(a.x) outputs "undefined".

3. Final Answer:

   undefined -> Option A

4. Quick Check:

   Compatible class instance property accessed correctly [OK]

Hint: Compatible class instances share accessible properties [OK]

Common Mistakes:

• Expecting runtime error due to extra properties
• Thinking assignment causes compilation error
• Assuming class properties are auto-initialized to 0

4. Given the code below, why does TypeScript show an error?

class A { x: number; }
class B { y: string; }

let a: A = new B();

medium

A. Because new B() is not a valid constructor call

B. Because class names differ

C. Because B has extra property y

D. Because B does not have property x required by A

Solution

1. Step 1: Check Property Compatibility

   Class A requires property x. Class B only has property y, so B instances lack x.

2. Step 2: Understand TypeScript Compatibility Rules

   TypeScript requires the assigned instance to have all properties of the target type. Missing x causes error.

3. Final Answer:

   Because B does not have property x required by A -> Option D

4. Quick Check:

   Missing required property causes error [OK]

Hint: Check if assigned class has all required properties [OK]

Common Mistakes:

• Thinking class names must match
• Assuming extra properties cause error
• Believing constructor call is invalid

5. You have two classes:

class Person { name: string; age: number; }
class Employee { name: string; age: number; salary: number; }

Which assignment is valid and why?
let p: Person = new Employee();
let e: Employee = new Person();

hard

A. Only let p: Person = new Employee(); is valid because Employee has all Person properties

B. Only let e: Employee = new Person(); is valid because Person has fewer properties

C. Both assignments are valid because classes share some properties

D. Neither assignment is valid due to different class names

Solution

1. Step 1: Compare Properties of Person and Employee

   Employee has all properties of Person plus salary. Person lacks salary.

2. Step 2: Check Assignment Compatibility

   Assigning Employee instance to Person variable is valid (extra properties allowed). Assigning Person instance to Employee variable is invalid (missing salary).

3. Final Answer:

   Only let p: Person = new Employee(); is valid because Employee has all Person properties -> Option A

4. Quick Check:

   Extra properties allowed, missing properties not [OK]

Hint: Assign subclass to superclass type, not vice versa [OK]

Common Mistakes:

• Assuming both assignments are valid
• Confusing extra vs missing properties
• Thinking class names affect compatibility