Showing posts with label Design Patterns. Show all posts
Showing posts with label Design Patterns. Show all posts

Saturday, 21 February 2026

Liskov Substitution Principle - SOLID Principle using C# in .NET10

In this article are going to see what is Liskov Substitution Principle, Objects of the super class can be replaced by objects of the sub classes with out breaking the correctness of the program..

We take one example we take Shape class where we have the Area method which will calculate the area, but when you see the Square which will break the behaviour, if the values are not Equal. the Values of the variable are needs to be Equal for Square

    internal abstract class Shape
    {
        public int Width { get; set; }

        public int Height { get; set; }

        public abstract int Area();
    }

    internal class Rectangle : Shape
    {
        public override int Area()
        {
            return this.Width * this.Height;
        }
    }

    internal class Square : Shape
    {
        public override int Area()
        {
            if(this.Width != this.Height)
                throw new InvalidOperationException("All sides
                        are must be equal for square");

            return this.Width * this.Height;
        }
    }

public class LiskovSubstitutionPrinciple
    {
        public void CalculateArea()
        {
            Shape obj1 = new Rectangle();
            obj1.Width = 10;
            obj1.Height = 20;
            obj1.Area();

            Shape obj2 = new Square();
            obj2.Width = 20;
            obj2.Height = 10;
            obj2.Area(); // Here Base class behaviour is broken because of exception
        }
    }


Liskov Substitution Principle

How we make this class to LSP, the Base class behaviour should not broke, so we slightly change the code which adhere to Liskov substitution principle.

    internal abstract class Shape
    {
        public abstract int Area();
    }

    internal class Square(int SideLength) : Shape
    {
        public override int Area()
        {
            return SideLength * SideLength;
        }
    }

    internal class  Rectangle(int Width, int Height) : Shape
    {
        public override int Area()
        {
            return Width * Height;
        }
    }

    public class LiskovSubstitutionPrinciple
    {
        public void CalculateArea()
        {
            List<Shape> shapes = new List<Shape>
            {
                new Square(7),
                new Rectangle(4, 6)
            };

            foreach (var shape in shapes)
            {
                Console.WriteLine($"Area of {shape.GetType().Name}: {shape.Area()}");
            }
        }
    }


From the above code you can learn what is Liskov Substitution Principle.

Monday, 16 February 2026

Open Closed Principle - SOLID Principle

In this article we are going to see what is Open Closed Principle (OCP) in SOLID.  OCP is open for extension and closed for modification. that means a class can be extended through override and not allow to modify.

we see Employee class in which GetSalary is used to fetch the salary this method can be override in Manager class which is derived from employee class but not allow to modify the employee class.



From this article you can learn the Open Closed Principle

Sunday, 15 February 2026

SOLID - Single Responsibility Principle

In this article we are going to see what is single responsibility principle (SRP) in SOLID. The SRP is about the class should have only one responsibility or we can say like it should talk about only one entity. For Example if it is a Employee class, then it should have behaviour and properties only about Employee. simply says the class should have only one reason to change.

First we will see a class which violating the SRP.


In the above class Salary we see that three methods

1. one is calculating Salary.

2. another one is save to DB

3. another one is Print to Salary. 

So the first one is application logic , second one is DB layer, third one is UI layer code, all are three different behaviour, now this is violating the SRP. 

How we can convert this to SRP.

Now if you see above example three classes in which each one have one responsibility, first one is business logic, second one is DB logic, third one is UI logic.

Now we can see a Logger class which is in SRP.


The above class is Logger, which have only one responsibility or talks about only one entity Logging message. if we have another method like  PrintMessage() in the class then that is irrelevant to the class then that is violating the SRP

Wednesday, 11 February 2026

Implementation of Repository pattern and Unit Of Work in .NET10 - Example 2

 In this post we are going to see the example 2 of implementation of repository pattern and unit of work in .Net10. we separate the project in to four layers. 

1. Domain or Entities

2. Application or UseCase

3. Infrastructure

4. Controllers

Dependencies:



Solution Structure

Domain or Entities:

  1. It is consists of Entities.
  2. It is consists of Repositories and Unit Of Work Interfaces.
Application or UseCase
  1. It is consists of declaration of Application Service Interfaces with public access.
  2. It is consists of Implementation of Application Services with internal access,
  3. Usage of Repositories in the Application Services
  4. To register the services in main program, we have to declare composition root.
Infrastructure
  1. Consists of implementation of Repositories and Unit Of Work with internal access, which can be changed easily,in the future so business logic wont get change, because the application layer work with abstractions.
  2. To register the repositories in main program we have to declare composition root.
Controller
  1. Uses the Register method from application layer and infrastructure layer.
Let we see this with example.

Domain:



Application or Use Case:



Infrastructure Layer:











Controllers:


From this article you can learn a example of how to implement the Repository pattern and Unit Of Work. 

Monday, 21 December 2015

Implement the Chain Of Responsibility design pattern in Javascript

In this post we are going to see the Implementation of Chain of Responsibility design pattern in Javascript, Chaining means when a object is executed a function furthurly from the result set we can executed another set of functions

Ex: $(".txt")..load().click().focus();

sample code:




How we can manipulate the chaining of methods against the objects. Basic structure of the Chain of  Responsibility pattern




var chainPatter = function () {

};

chainPatter.prototype = {
    method1: function () {
        return this;
    },
    method2: function() {
        return this;
    }
}


From the above sample structure we are going to create a real one.



/* Chain of Responsiblity */
var HtmlEle = function (elementinp) {
    this.elementT = elementinp;
};

HtmlEle.prototype = {

    attachEvent: function (eventname, fun, capture) {
        _hook(this.elementT, eventname, fun, capture);
        return this;
    },
    click: function (fun) {
        this.attachEvent("click", fun, false);
        return this;
    },
    load: function (fun) {
        this.attachEvent("load", fun, true);
        return this;
    },
    blur: function (fun) {
        this.attachEvent("blur", fun, true);
        return this;
    },
    focus: function (fun) {
        this.attachEvent("focus", fun, true);
        return this;
    },
    windowLoad: function (fun) {
        this.attachEvent("DOMContentLoaded", fun, false);
        return this;
    },
    value: function () {
        return this.elementT.value;
    }
};



object of Htmlele is used to create a instance against the element then we can chaining the functions against the element.

How we can chaining the methods in the object, let we some code, then we see the real sample code.


new HtmlEle(document).windowLoad(fun).focus(fun);

 var fun = function (){
     console.log("called"); 
 }

Code:



/* using the chaining method in Module pattern*/
var HtmlParser = (function () {

    /* private construction */
    function findType(tagname) {
        var _searchType = tagname.substring(0, 1);
        if (_searchType == ".")
            return "class";
        else if (_searchType == "#")
            return "id";
        else
            return "tag";
    }

    return {
        GetValue: function (elementT) {
            var _type = findType(elementT);
            var _element;
            switch (_type) {
                case "class":
                    _element = document.getElementsByClassName(elementT.substr(1));
                    break;
                case "id":
                    _element = document.getElementById(elementT.substr(1));
                    break;
                case "tag":
                    _element = document.getElementsByTagName(elementT);
                    break;
            }

            return _element.value;
        },
        _element: function (elementT) {
            var _type = findType(elementT);
            var _element;
            switch (_type) {
                case "class":
                    _element = document.getElementsByClassName(elementT.substr(1));
                    break;
                case "id":
                    _element = document.getElementById(elementT.substr(1));
                    break;
                case "tag":
                    _element = document.getElementsByTagName(elementT);
                    break;
            }
            return new HtmlEle(_element);
        },
        _loadDocument: function (fun) {
            return new HtmlEle(document).windowLoad(fun);
        }
    }

})();



/* chain pattern to load the document and pass the callback */
HtmlParser._loadDocument(function () {

    var buttonEle = HtmlParser._element("#check");

    buttonEle.click(function () {
        alert(HtmlParser._element("#test1").value());
    })
        .focus(function () {
            console.log("focus");
        });

    HtmlParser._element("#bdy").load(function () {
        console.log("body loaded");
    });

    HtmlParser._element("#div1").blur(function () {
        console.log('out of focus');
    })
        .click(function () {
            console.log("div clicked");
        });

});





From this post you can learn how to create a Chain of Responsibility design pattern in JavaScript.