[Golang] Adapter | Adapter pattern in go | go Adapter pattern

[Golang] Adapter Adapter pattern in go go Adapter pattern
This video contains information about Adapter design Pattern in Go:
1. What is golang Adapter Design Pattern ?
2. Why we use Adapter Design Pattern ?
3. How to implement Adapter Design Pattern in Go ?
GitHub:
github.com/Roh...
⭐ Tags ⭐
We Build Developers
Adapter Pattern in go
Golang Adapter pattern
design patterns
Design Patterns in Go
Go Design Patterns

[@RSX-0806]

I was struggling to grasp the abstract idea of Adapter pattern, you really explained it very well. thank you

[@webuilddevelopers]

Thank you this means a lot....

[@jonesgabriel9337]

Just landed on this playlist. this is a Gold mine !

[@webuilddevelopers]

Glad to hear this

[@Tyronekong]

As mentioned below, what is the benefit of creating an adaptor as opposed to creating another struct which implements the mobile interface and passing that into the client?

[@Tyronekong]

type Mobile interface { chargeMobile() } type Client struct { } type Apple struct { } func (c *Client) charging(m Mobile) { m.chargeMobile() } type Android struct { } func (a *Apple) chargeMobile() { fmt.Println("charging apple mobile") } func (a *Android) chargeMobile() { fmt.Println("charging android mobile") } client := &Client{} apple := &Apple{} android := &Android{} client.charging(apple) client.charging(android)

[@anujjain9273]

you can also add notes for pro's and con's or articles related to it . Also explanation was nice , watched 7-8 videos of this playlist , looking forward to finish the playlist

[@webuilddevelopers]

Thank you

[@Okotherapy]

Thank you, it still helps people)

[@kirakira160]

keep going sir! looking for more videos

[@webuilddevelopers]

Sure thing, thanks

[@dileeshaabilash5562]

perfect ❤❤

[@ankitchahal7238]

Excellent video, one question Can we implement an adapter design pattern without giving concrete implementation?

[@webuilddevelopers]

Nice question, if you are following interface approach then concrete implementation is must, but if you donot follow interface approach then no concrete implementation is required, hope this answer your query...

[@AtishAbhang]

why can't we just create android struct which implements charge function, that becomes part of the interface and just pass android struct to charge function accepting mobile interface?

[@Tyronekong]

This was my exact thought, what is the benefit of creating an adaptor as thats extra code for doing the same thing

[@rifajas]

poor naming conventions used and confusing method names are used. If our intention is to charge the mobile, the mobile interface could be renamed as charger and the chargeAppleMobile method also could be renamed as charge to avoid confusion and later on we can introduce the android adapter which implements charger interface.

[@amantarar9077]

are you the guy works in ticketMaster ?

[@ArshEducation]

Names used are really confusing. Had to watch this twice to understand what do you actually mean. Other than this, nice video

[@webuilddevelopers]

Thank you for the genuine feedback I will take care of this moving forward........