gomock
validator
gomock | validator | |
---|---|---|
40 | 68 | |
9,010 | 15,640 | |
- | 1.8% | |
2.5 | 7.4 | |
11 months ago | 11 days ago | |
Go | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gomock
- Maintainership of Go’s official gomock repo has been transferred to Uber.
- Uber Now Maintains Gomock
-
Google Stopped Maintaining GoMock
The commit mentions this rather sad thread: https://github.com/golang/mock/pull/627#issuecomment-1605169...
-
Tools besides Go for a newbie
IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
-
When to mock and what to mock in a Web API?
Normally I like to generate everything with Mockgen and test it using table driven test.
-
Is gomock still maintained and recommended?
Looking at gomock's commit history, it seems like there hasn't been much activity on the project in a couple of years. I'm wondering if this is the case of software being mostly done and just in maintenance mode, or if gomock is falling behind. The reason I fear for the latter is there are still issues being opened up that don't seem to be engaged very much.
-
Want to know if this is a valid approach
Yeah, that would work just fine. Nevertheless, as your business logic gets more complicated, you will want to test more scenarios and mocks will get complicated fast. In these cases tools like gomock really shine and make your life easier. I understand that this is a just-for-fun project, but it's never too early to experiment with a popular solution, especially if you plan on using Go professionally in the future.
-
Go API Project Set-Up
Unit tests are leveraged to test individual units of code. As such it is not recommended for a developer to scaffold entire dependencies for the sake of testing a single object. Due to the way Go's specific implementations work, I've learned over time to declare interfaces for a lot of the structs that I use in Go. Interfaces not only define a contract for which struct-based implementations should adhere, but they also provide a mechanism for which struct methods can be mocked. While I've experimented with the mock package in testify, I've come to prefer the mock functionality which is provided by mockgen.
-
Comprehensive Guide to Testing in Go
gomock can also be great for testing when used sparingly. Mocking out one or two calls is great, anymore than that and it becomes exponentially harder to reason about
-
Google's internal Go style guide
Where we do use mocks, we primarily use GoMock.
validator
- API completa em Golang - Parte 7
- API completa em Golang - Parte 3
-
Is there any equivalent to pydantic, serde, etc?
go-playground/validator
- API completa em Golang - Parte 1
-
API validation in Gin: Ensuring Data Integrity in Your API
If you want to know all the available validation in Gin. Then you can look at this package because Gin uses this package under the hood. Package: https://github.com/go-playground/validator Specific-file: https://github.com/go-playground/validator/blob/master/baked_in.go#L73
-
Yet another validator 0.9.5
Now it has most of the Playground validator's common checks and a few own tricks.
-
Openapi server generation
In Go I've found this package - https://github.com/go-playground/validator. It seems popular in the community, but it is tag-based. It looks like if I wanted to use it - I would have to basically duplicate structs.
-
Validator in handler or domain
so I am working on a ecommerce api as a hobby project which is mostly inspired by wtf dial project I like to use validator package to remove boilerplate over my domain package for example take a look https://github.com/mortezadadgar/ecommerce-api/blob/b0bf43d042d62fdca1c2d097ec51b05bc539cef2/domain/users.go#L33 I have to option either add validate.Struct() to my domain which is suggested to avoid by author of wtf peoject or add it to handler which I doubt is a good idea as it's not in business logic of handler and makes unit testing harder
-
Request Validations in Go REST API
I use https://github.com/go-playground/validator, but honestly, I am not a fan. I just haven’t found anything better.
-
Tools besides Go for a newbie
IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
What are some alternatives?
mockery - A mock code autogenerator for Go
ozzo-validation - An idiomatic Go (golang) validation package. Supports configurable and extensible validation rules (validators) using normal language constructs instead of error-prone struct tags.
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
govalidator - [Go] Package of validators and sanitizers for strings, numerics, slices and structs
pgx - PostgreSQL driver and toolkit for Go
grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC
sqlx - general purpose extensions to golang's database/sql
viper - Go configuration with fangs
counterfeiter - A tool for generating self-contained, type-safe test doubles in go
uuid - Go package for UUIDs based on RFC 4122 and DCE 1.1: Authentication and Security Services.
go-sqlmock - Sql mock driver for golang to test database interactions
fiber-swagger - fiber middleware to automatically generate RESTful API documentation with Swagger 2.0.