mapstructure VS Testify

Maybe https://github.com/mitchellh/mapstructure can do what you want? It has some options for Remainder Values and Omit Empty

I've tried using mapstructure to then marshal the map fields into a struct which mostly works (it struggles with times and custom time types which requires a workaround for each case), but this doesn't feel very idiomatic and requires two passes at marshaling.

Although some orders may have more records maybe a superset can be indentified that you can actually create a struct of it and after gathereing first all values into a map then convert it to a struct maybe using a library like https://github.com/mitchellh/mapstructure . this way you can at least isolate the non structured data only on the data extraction part and the rest of your application can work with well formed structs.

Alternatively, you could try https://github.com/mitchellh/mapstructure if you don't know what your incoming structure is

I'm doing it by validating a map[string]any first then putting it into a structure using mapstructure. It covers most use-cases and offers the most flexibility, at the expense of a bit of performance.

That said, it is possible to do this with JSON using something like https://github.com/tidwall/gjson or if you are fine with the switch statement but don't want to marshal and unmarshal again: https://github.com/mitchellh/mapstructure

https://github.com/mitchellh/mapstructure because we have JSON documents which contain rugged arrays ;-)

I've been using mapstructure.Decode to great effect, but currently can't figure out why a given mapping doesn't work. I'd appreciate it if someone could point out wtf I'm doing wrong or at least in the right direction:

What do you mean by "decode"? I've used https://github.com/mitchellh/mapstructure but that doesn't quite look like what you're doing.

github.com/stretchr/testify

I then verify that there are no issues with writing the body with require.NoError() from the testify toolkit. This will ensure the test fails if something happens to go wrong at this point.

For testing purposes, Go provides a go test command that automatically discovers tests within your application and supports features such as caching and code coverage. However, if you require more advanced testing capabilities such as suites or mocking, you will need to install a toolkit like testify. Overall, while Go provides a highly effective testing experience, it's worth noting that writing tests in Python using pytest is arguably one of the most enjoyable testing experiences I have encountered across all programming languages.

Things I can't live without in a new Go project in no particular order:

- https://github.com/golangci/golangci-lint - meta-linter

- https://goreleaser.com - automate release workflows

- https://magefile.org - build tool that can version your tools

- https://github.com/ory/dockertest/v3 - run containers for e2e testing

- https://github.com/ecordell/optgen - generate functional options

- https://golang.org/x/tools/cmd/stringer - generate String()

- https://mvdan.cc/gofumpt - stricter gofmt

- https://github.com/stretchr/testify - test assertion library

- https://github.com/rs/zerolog - logging

- https://github.com/spf13/cobra - CLI framework

FWIW, I just lifted all the tools we use for https://github.com/authzed/spicedb

We've also written some custom linters that might be useful for other folks: https://github.com/authzed/spicedb/tree/main/tools/analyzers

Im thinking in wrap or not the library https://github.com/stretchr/testify to do my tests.

Are you limited to the std lib, or can you use testify? You can require things like require.Error()

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

To answer OP directly, I am largely quite happy with mockery (and testify) to write expressive tests.

Como herramientas te recomiendo: FastJson https://github.com/valyala/fastjson : Si necesitas leer jsons Testify https://github.com/stretchr/testify : Para mockear y testear