Even though I barely got my hands dirty with #golang I really enjoy working with #fiber and #entgo for #REST APIs so far.

Would be nice to autogenerate entities/endpoints via #OpenAPI definition so I end up having Ent schema structs and Fiber endpoints πŸ€”

#dev #webdev

I've read mixed things about #gorm and now looking up #entgo instead.

Gorm doesn't feel very ergonomic to use for me and the lack of being able to add the migrations to version control isn't great.

What's your take on this? Or what do you usually use when it comes to database libraries?

#golang #gophers

@samebchase I like the ent framework which supports GraphQL and OpenAPI and maybe other things
https://entgo.io/
#EntGo #GoLang
ent

I have found two more things about #entgo that I find a bit icky:

1. Because all mutations have to go through entity builders, it's not possible to create an entity from a struct like `db.User.Create(user).Save(ctx)`, you need to call SetXxx() methods on the builder for all the fields.

2. Adding convenience/helper methods to entities is not straight-forward and require defining awkward code templates.

That being said, I still think it's a good and very powerful framework!

#golang