Design Patterns: Adapter

In this blog we will learn when we should use the adapter in Design patterns.

The adapter is used when you want to integrate a class from another source into your code.

It could also be used to enable the use of legacy classes into your new architecture. It can also be used with classes that needs very specific methods to complete some work, like database access classes, and then they could be adapted to use a common interface.

Imagine the following situation

You have a game where all your characters inherit from the abstract class Character.

public abstract class Character
{
    public int Health { get; set; }

    public int Mana { get; set; }

    public abstract string Attack();
}

public class Link : Character
{
    public override string Attack()
    {
        return "Link Attack";
    }
}

public class Zelda : Character
{
    public override string Attack()
    {
        return "Zelda Attack";
    }
}

You then need to include a character from another game into your game, but you can’t change the original class. So you can create an adapter for it:

public class Mario
{
    public string JumpAttack()
    {
        return "Mario Attack";
    }
}

public class MarioAdapter : Character
{
    private Mario mario = new Mario();

    public override string Attack()
    {
        return mario.JumpAttack();
    }
}

This way you can use the new character as if it were just another normal character in your game.

Character link = new Link();
Character zelda = new Zelda();
Character mario = new MarioAdapter();

Console.WriteLine(link.Attack());
Console.WriteLine(zelda.Attack());
Console.WriteLine(mario.Attack());

Outputs:

Link Attack
Zelda Attack
Mario Attack

This way it is possible to adapt different classes to use the same interface or abstract class, so your application doesn’t need specific handling for different types.