What is Liskov Substitution Principle ?

[@happymalyo_]

Your tutorial is incredibly clear and well-organized! Keep creating more video like this

[@interviewhappy]

Thanks buddy and all the best for your career.

[@ankitaburman5406]

Excellent Explaination Sir. Thank you so much for videos on Solid Principles

[@interviewhappy]

Thanks Ankita and all the best for your career.

[@nathanyt]

A better example would be something like this:
- You have a function that accepts an Employee object ---- *void CalcSalary(Employee e) { e.CalculateSalary() }*
- If you are following LSP, if I pass a subclass object to that function, the program should sill work. Example: *CalcSalary(new PermanentEmployee())*

[@nayankulkarni5131]

What a absolute simple explaination!

[@rasalshukla4046]

Wow wow wow in 7 min you have solved my confusion

[@manishackadam]

Awesome!! understood n will remain permanent in my memory

[@aneesmohammed7978]

Hi. Superb explanation. You have explained in clarity and simple words which I hardly found from others

[@interviewhappy]

Thank you so much 🙂

[@adventurer2395]

this is a better example of interface segregation than LSP

[@chandusrinivas7813]

Wow, very simple and best example, Great explanation.
Thanks Bro.

[@interviewhappy]

Glad you liked it!

[@anooprawat1006]

What if you return 0 bonus, instead of throwing exception?, Does it fix Liskov ?

[@prakash13565]

no it will not as you are breaking the functionality here. See for caluclating a salary we have a particular formula same for bonus and that method will be defined in the parent class. Here in the video he said he is not caluclating just returning the values it means formula will be same for all the employees. But in case for contract employe we cant give bonus and we have to redefine the defination of that bonus method which is wrong.

[@ijaztufail8000]

Very good sir keep it up. You are explaining at its best. Please upload repository patterns series after this series

[@interviewhappy]

Thanks @ ijaz Will try to do it.

[@ijaztufail8000]

@@interviewhappy Welcome. And one more thing please make videos on some programmatic/written questions for experienced developer like in SQL and C# LINQ or other type of test questions

[@Gauravkumar-jm4ve]

Very good pls upload more, thanks so much for sharing ur valuable knowledge

[@interviewhappy]

Thanks Gaurav and all the best for your career.

[@srinivastirri9799]

Excellent neat and clean explanation

[@interviewhappy]

Thanks, glad you found it helpful!

[@shenth27]

This example violates LSP because you're throwing NotImplementedException but you can instead returns 0 bonus for ContractualEmplyeee and avoid the error.

[@visarad]

same question

[@surajmangalekar4370]

0 has a value, business perspective we should not provide anything for contract employees

[@akdigitalmedialive]

Returning 0 means there is salary component bonus which is wrong. Also think about maintaining this method in long term

[@sanmathi3968]

Awesome. Really helped. Please create videos for design patterns 😊

[@haidernaqvi87]

It is somewhat similar to interface segregation principle. Because contractaul employee were forced to implement bonus method which it doesn’t need

[@interviewhappy]

It is bit similar but not the same.

[@gawnsj]

So we just need to move calculateBonus inside permanentEmployee class right?

[@na2599]

we can say that LSP is same as Interface segragation Principal?

[@khilanunadkat3865]

Excellent explanation. Thank you

[@interviewhappy]

Thanks. Glad you liked it. Wish you all the best for your career.

[@chirasreepal2672]

simple and clear explanation :)

[@sweetu246]

Sir ,Videos really helped me to understand the concepts,Please create azure tutorial as well

[@MuhammadKashif-wh1us]

just one word : Thanks

[@interviewhappy]

Your Welcome @kashif

[@anandafit6]

what are the practical scenarios we need to replace supertype from subtypes?

[@User-Dotnet]

What will happen if we not Override Bonus Method in ContractualEmployee Class? What will happen if we declare only Calculate salary because Bonus method already override in PermanentEmploye Class right!

[@rktamilarasi2442]

I have one doubt
We can't use the CalculateBonus() method in ContractualEmployee class but it is basically have the method of CalculateBonus() through inheritance.
Then my question is how to use CalculateBonus () method in ContractualEmployee class and ContractualEmployee class object?

[@muhammadadil7307]

Sir its humble request plz make video on deep and shallow copy

[@S-yf5te]

The above example is for bad design how to fix it?

[@mayankpriyadarshi9346]

I am confused you have created object of pEmployee.calculateBonous and saying this follow LSP. Help me to correct if CalculateBonous will be there in PermanentEmployeeClass as it is there in base class then only it follows LSP.
LSP : whatever methods is there in parent class that should be there in child class and child class should not change the behavior of parent class object .

[@sauravpati8597]

can you make some videos on Architecture interview questions

[@zeez7777]

Why not just return 0 for the bonus?

[@sureshkumar5103]

Well explained. Thanks a lot.

[@interviewhappy]

Glad you liked it

[@ravindrareddy-x7p]

great explanation

[@srikanth29]

If we return 0 in the bonus method of contractEmployees method then we wont' voilate.

[@ravichandra786]

Good explanation😊

[@interviewhappy]

Thanks @ Ravi . Glad You Liked it

[@rishavraj3127]

Simply WOW 👌👌👌👌

[@interviewhappy]

Thanks a lot 😊

[@Skgupta2353]

yes sure

[@ravindran7956]

I feel this is not proper example for LSP

[@interviewhappy]

np

[@Rahulsingh-ce1hd]

please provide your version of LSP sir, so that we all can learn.

[@compman73]

Not a correct explanation of LSP
You need to cast child to parent variable

[@jsm33t]

Thankyou!!!!!!

[@interviewhappy]

You're welcome! @JSM33TMUSIC

[@biswajitmishra3461]

excellent