gogo-factory VS errors

Are there people seek a fixture replacement package like factory_bot (a ruby gem)? I build a similar package (gogo-factory). It is helpful to setup test data.

When I switch language from ruby to golang, I desired to have an alternative to factory-bot (a ruby gem). Therefore, I found the go-factory which can be used to build random object for testing. After using it for a while, I decide to build another fixtures replacement package which is gogo-factory.

Can you explain why we should this over https://github.com/pkg/errors?

The pkg/errors package offers some nice add-ons for easier error handling. Too bad it was put into maintenance mode pending whatever changes/improvements are coming in Go 2.

I can't figure out the issue so here for some help, I am using `neovim/nvim-lspconfig` my `gopls` doesn't recognise external paths such as `github.com/pkg/errors` , it throws error`could not import github.com/pkg/errors (cannot find package "github.com/pkg/errors" in any of /usr/local/go/src/github.com/pkg/errors (from $GOROOT) /Users/ra compiler (BrokenImport)\`

Also - there are some error handling utils that allow you to wrap errors before passing: https://github.com/pkg/errors

Should've been something like errors.Newf("failed to foofoo %s", foo) instead and preferably never invent %w but have some controlled way to wrap like errors.Wrapf(err, "failed to foofoo %s", foo) that was in ye olde github.com/pkg/errors.

Prefer using errors.Wrap and errors.Wrapf from https://github.com/pkg/errors . It's frozen because they don't want to add features, waiting for a re-write of error handling in Go2.

Im using zerolog and in order to get the stack trace for my error I have to wrap my error in errors.Wrap from "github.com/pkg/errors".

And for "real programs" you can use https://github.com/pkg/errors (if you want stack traces)