Bridge.cs

namespace DesignPatterns.Structural.Bridge;

/// <summary>
/// Bridge Pattern
///
/// Intent: Decouple an abstraction from its implementation so that the two can vary independently.
///
/// When to use:
///   - When you want to avoid a permanent binding between an abstraction and its implementation
///   - When both the abstractions and their implementations should be extensible by subclassing
///
/// Real-world analogy: A TV remote — the remote (abstraction) works with any TV brand (implementation)
/// via a common interface. You can change remotes or TVs independently.
/// </summary>

// TODO: Implement Bridge
// 1. Implementation interface (e.g., IDevice)
// 2. Concrete implementations (e.g., TV, Radio)
// 3. Abstraction class that holds a reference to the implementation
// 4. Refined abstractions (e.g., AdvancedRemote)