How To Refactor A Golang Project By Using Interfaces

[@anthonygg_]

► Join my Discord community for free education 👉 discord.com/invite/bDy8t4b3Rz ► Become a Patreon for exclusive tutorials 👉 www.patreon.com/anthonygg_ Thanks for watching

[@jondoe79]

You can use space separated tags `bson: "fact" json:"fact"` Documentation says: By convention, tag strings are a concatenation of optionally space-separated key:"value" pairs. Each key is a non-empty string consisting of non-control characters other than space (U+0020 ' '), quote (U+0022 '"'), and colon (U+003A ':'). Each value is quoted using U+0022 '"' characters and Go string literal syntax.

[@anthonygg_]

You are my hero 🙏

[@Cethris]

"This is going to be nice and thick for the blind homies" I nearly choked

[@rekram1519]

I was hoping youd make this type of video, perfect!!!

[@TheWorpler]

Just found you and subbed. Moving to use Go on some personal projects rather than Python.

[@anthonygg_]

Welcome to the club!

[@tpotjj2979]

Interfacer all the way🚀

[@donovanvanderlinde3478]

Lol I just blew all my money for December 😂 But now I know which Patreon to sub to in Jan … your content is insane

[@anthonygg_]

Thanks my man!

[@salman0ansari]

finally found a good gotuber 😮‍💨

[@zeusdeux]

GSP is a golang degen?! Noice

[@hananasyrawi5206]

Yeah Power of Type Duck

[@ZockaRocka]

Hey :) I am sure you answered the question a lot of times, but i would like to know which Font and Theme do you use? thanks in advance! Great Vid!

[@goriunovd]

HI Anthony, really love your videos, just found the channel today been going to quite a few How To Golang videos and find it very helpfull! I was actually wondering how would you approach an API design that requires you to do partial update, and been able to reset the value of some fields: For example lest say we have the CatFacts struct that looks like type Fact struct { ShortForm string LongForm string } type CatFact struct { Fact Fact Length int } Let say I would call the api to create the fact like POST {fact: { shortForm: "one", longForm: "super long form"}, length: 20 } But then later I want to update the fact with PATCH {fact: { shortForm: "two", longForm: "super long form"}} and again update it with PATCH {fact: null} or update just Length PATCH {length: 1000} This is just an example but I would really like to know how would you structure your structs and application for this cases, I know that golang treats null and no value the same so it becomes trickier to set value to Null, also the null packages do not support non primitive types. Would really appreciate your help!

[@failist9570]

Came here from reddit. Stayed here for content.

[@lviv255]

Interface still has the CatFact as an arg. An interface should not have any reference to concrete types else it defeats the main advantages of using it.

[@JustValxntine]

What's the other option here? CatFact is a type that we own and control, not a dependency

[@pedrohenriquebufulindealme5763]

Great Video. I was wondering, what if you want to have multiple different collections for MongoStorer? For example, a "facts" collection and a "breeds" collection in this case. Could I compose my interface by kind of creating a repository pattern? Where I Have multiple interfaces inside my MongoStorer where each one have it's GetById, Update... for that specific collection?

[@anthonygg_]

Thats possible!

[@shayannadeem321]

Can you create a video that tells how to use interface with 2 or 3 different type of structs as if you have multiple structures the interface will have multiple CreateAccount, CreateCatfact and methods for each type of struct ? can we use interface{} or any in interfaces ?

[@Cruzylife]

can u push this to your github

[@murodiskandarov2431]

no comment