https://jholjhapata.com/index.php?action=history&feed=atom&title=Interface_Segregation_Principle 2026-05-17T04:27:49Z Revision history for this page on the wiki MediaWiki 1.33.0 https://jholjhapata.com/index.php?title=Interface_Segregation_Principle&diff=37&oldid=prev 2019-08-15T15:36:38Z

<p>Created page with &quot;The &#039;&#039;&#039;Interface Segregation Principle&#039;&#039;&#039; states that no client should be forced to depend on methods it does not use. Do not add additional functionality to an existing inte...&quot;</p> <p><b>New page</b></p><div>The '''Interface Segregation Principle''' states that no client should be forced to depend on methods it does not use.<br /> <br /> Do not add additional functionality to an existing interface by adding new methods. Instead, create a new interface and let your class implement multiple interfaces if needed.<br /> <br /> == Interface Segregation Principle Example ==<br /> Let’s take a look at an example of how to write a piece of code that violates this principle.<br /> <br /> interface IPost<br /> {<br /> void CreatePost();<br /> }<br /> interface IPostNew<br /> {<br /> void CreatePost();<br /> void ReadPost();<br /> }<br /> <br /> In this example, let’s pretend that I first created IPost interface with the signature of a CreatePost() method. Later on, I modify this interface by adding a new method ReadPost(), so it becomes like the IPostNew interface. This is where we violate the '''Interface Segregation Principle'''.<br /> <br /> Instead, simply create a new interface.<br /> <br /> interface IPostCreate<br /> {<br /> void CreatePost();<br /> }<br /> interface IPostRead<br /> {<br /> void ReadPost();<br /> }<br /> <br /> If any class might need both the CreatePost() method and the ReadPost() method, it will implement both interfaces.</div>

Admin