resty
gomock
resty | gomock | |
---|---|---|
11 | 40 | |
9,382 | 9,010 | |
1.5% | - | |
7.8 | 2.5 | |
16 days ago | 10 months ago | |
Go | Go | |
MIT License | Apache License 2.0 |
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.
resty
-
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
-
Network Error Handling
We have faced several network issue on our backend application written in golang with resty for inter service calls. We have seen large amount of network errors like `EOF, unexpected EOF, http: stream closed` because of which our APIs fail. Have you faced similar issue and what were the solutions you've implemented.
- Those who use an http client on top of/instead of the built in http package, what do you use and why?
- Libraries you use most of your projects?
-
Best packages?
Go-resty makes it a lot easier to create a http client and much more readable for developers.
-
How do I see the full details of an http request I send?
I don't use the simple http whenever i need to call any API from code . I just use resty its fairly easy to use and logging requests with it is quite easy
-
qst: an *http.Request builder
What are the advantages over https://github.com/go-resty/resty ? resty has `.R()` request builder.
-
Building microservices in Go with Gin
We need to call PrinterService from the InvoiceGenerator. Therefore, we need an HTTP client in our project. Install Go’s resty HTTP client library with the following command.
-
Any http client framework?
Check out https://github.com/go-resty/resty
-
Binance API
I used to use the standard http lib, but now I switched to resty https://github.com/go-resty/resty
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.
What are some alternatives?
gorequest - GoRequest -- Simplified HTTP client ( inspired by nodejs SuperAgent )
mockery - A mock code autogenerator for Go
sling - A Go HTTP client library for creating and sending API requests
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
go-retryablehttp - Retryable HTTP client in Go
pgx - PostgreSQL driver and toolkit for Go
hub - A command-line tool that makes git easier to use with GitHub.
sqlx - general purpose extensions to golang's database/sql
fastlz - Wrap over FastLz for GoLang
counterfeiter - A tool for generating self-contained, type-safe test doubles in go
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
monkey - Monkey patching in Go