Part5 || Fourth SOLID Principle -- Interface Segregation with Example
It's the fourth principle of SOLID -- Interface segregation, On this principle
A client should never be forced to implement an interface that it doesn’t use, or clients shouldn’t be forced to depend on methods they do not use.
Here, it’s about how to write interfaces. So what is stated? Basically, once an interface is becoming too large/fat, we absolutely need to split it into small interfaces that are more specific. And interface will be defined by the client that will use it, which means that client of the interface will only know about the methods that are related to them.
-------------------------------------------------------------------------------------------------------------------
Last and the 5th Principle of SOLID will come soon please stay tied and safe.
If you are new to our channel then Pleas check our other videos and don't forget to share with your college or friends if you find this helpful to you.