SOLID Principles in JavaScript

What SOLID principle suggests that a derived class should be able to replace its base class without breaking the application?

class File {
  read(): string { return 'file content'; }
  write(content: string): void { /* write content */ }
}

class ReadOnlyFile extends File {
  write(content: string): void {
    throw new Error('Cannot write to read-only file');
  }
}

Single Responsibility Principle
Open/Closed Principle
Liskov Substitution Principle
This code violates the Liskov Substitution Principle (LSP). The ReadOnlyFile class breaks the contract established by its base File class by throwing an error in the write method. According to LSP, if a program is using a base class, it should be able to use any of its derived classes without knowing it. A better design would be to separate read and write capabilities into different interfaces.
Interface Segregation Principle

Next Question (15/20)