S.O.L.I.D Design Patterns - Unity - Liskov Substitution Principle

Показать описание

Just Here To Plug My Social Media Stuff:

Рекомендации по теме

Комментарии

That was a good example. Thanks! I also learned a peripheral trick from you about printing variables in curly brackets. Thanks for that too!.

judgegroovyman

Oh awesome. I was already using this without even knowing it was a named principle. Neat.

feidry

This misses the main point of LSP, this is an example of OCP. LSP is mainly meant to uncover poor uses of inheritance.

Research the "Circle-Eclipse / Square-Rectangle" problems to see examples of what LSP solves.

Sorry, not trying to be rude to you man but for correctness, people should know. I appreciate this video series as it's been a very helpful jumping off point for researching into SOLID.

curtiss

This is not a correct representation of the LSP, the principle stated that object of the parent class should be replaceable by object of the child class without breaking the code.

I'm not hating, I do like your videos but you're spreading the wrong information.

taoge

Great video. One question though: In your example of using an ItemLogger, wouldn't it be the responsibility of the ItemLogger to Debug.Log the data and just fetch the appropriate data to log from the Item? IE This way if we decided later down the road to log to a text file, we don't need to open all the item classes and change them?

MQNGameDev