Hmm, having a method on a class that when called won’t do what its name implies is just bad… really, really bad. anytime you see code that takes in some sort of baseclass or interface and then performs a check such as “if (someObject is SomeType)”, there’s a very good chance that that’s an LSP violation. I’ve done that, and I know so have you, let’s be honest.
Sometimes, solid principles go hand in hand.
https://softwareengineering.stackexchange.com/a/431254/293140
- Calaudio Lassala
No comments:
Post a Comment