From 5ed4f4da1d62a58db1716d0cf8dcadcd83aaa272 Mon Sep 17 00:00:00 2001 From: Bobby Cahill Date: Mon, 29 Apr 2019 15:01:12 -0400 Subject: [PATCH] Fix typo in SOLID Liskov subheading For the Audio and Video classes to be children of the FileInterface interface, and for the Liskov Substitution Principle to apply, they must implement the FileInterface interface. --- _posts/06-03-01-Complex-Problem.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/06-03-01-Complex-Problem.md b/_posts/06-03-01-Complex-Problem.md index ad7de84..297ddf1 100644 --- a/_posts/06-03-01-Complex-Problem.md +++ b/_posts/06-03-01-Complex-Problem.md @@ -51,7 +51,7 @@ the parent class’ type definitions.” Or, in Robert C. Martin’s words, “S types.” For example, if we have a `FileInterface` interface which defines an `embed()` method, and we have `Audio` and `Video` -classes which both implement the `embed()` method, then we can expect that the usage of the `embed()` method will always +classes which both implement the `FileInterface` interface, then we can expect that the usage of the `embed()` method will always do the thing that we intend. If we later create a `PDF` class or a `Gist` class which implement the `FileInterface` interface, we will already know and understand what the `embed()` method will do. The largest benefit of this approach is that we have the ability to build flexible and easily-configurable programs, because when we change one object of a