My experience of Golang is that dependency injection doesn't really have much benefit. It felt like a square peg in a round hole exercise when my team considered it. The team was almost exclusively Java/Typescript Devs so it was something that we thought we needed but I don't believe we actually missed once we decided to not pursue it. If you are looking at OpenAPI in Golang I can recommend having a look at... - Source: Hacker News / 2 months ago

See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated. Source: 7 months ago

If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/. Source: about 1 year ago

Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with: - Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go... - Source: Hacker News / about 1 year ago

One of the biggest issues I see is that you are using the same models for API as you are for the database. That wouldn’t fly in a real work system. And even though your doing simple CRUD I would introduce another layer for business logic. You should never have the Controller calling you database code directly. It never “stays” that simplistic. One of the easiest ways to deal with this is to use... Source: about 1 year ago

FYI: The zola.com part of the invite is standard. You have to either remove it or replace it. The save the date was legit. Source: about 1 year ago

Received phone invitation to a wedding through zola.com to click lead me to an application as an attendee. Ok I get it they want people to get onto a gift registry but they're asking for my Address e-mail, phone, social security, NOoooo... I know nothing about them. Do they sell my info? Source: over 1 year ago

Only having your name is fine. The issue I have is calling this a bridal shower invite when it's a tea party. And, then having the zola.com phrasing. A tea party is not a shower and mentioning gifts for a tea party is not a thing. Source: almost 2 years ago

I vote for number 4! I think the material/silhouette of number 2 would usually be a pretty safe bet, but the pattern is so light that it could very easily photograph as white, which is a thing you want to avoid. Try to find out what time the ceremony and where it's at from your boyfriend - if it's going to be outdoors or at a secular venue, you're probably ok, but if it's at a fancier venue or a church, you may... Source: about 2 years ago

Thanks for your reply. I always assumed it was a private residence as well. I recently stumbled across two weddings listed on zola.com that had that specific Bishop house listed as the wedding venue so that sparked my curiosity. Thanks again for your feedback. Source: over 2 years ago