goderive VS jennifer

I found https://github.com/awalterschulze/goderive but haven't used anything like it besides mockgen

Now, am I going to do the same with a library like goderive just so I can use FP techniques to get, amongst some other things, less nil checks? No. Probably not. If I wanted to use primarily FP techniques in my code, I would probably be using something else in the first place. Go isn't a great environment for guaranteeing immutability for starters, so anything like that is necessarily going to be an incomplete experience. And in the bargain, my code would, in my opinion at least, be less readable and maintainable.

We have a repo/library called fasten-sources which is made up of mostly generated code (using dave/jennifer)

Check out my https://github.com/dave/rebecca package for a neat way of building readme docs by embedding Go docs and examples. It generates the readme for https://github.com/dave/jennifer (see https://github.com/dave/jennifer/blob/master/README.md.tpl).

The design of the wrapper functions meant we couldn’t easily unmarshal the CUE value into the wrapper functions. This meant we needed to generate unmarshalled functions for the config types. We use the excellent Jennifer library by Dave (no really; github.com/dave/jennifer) for generating Go files.

I've used https://github.com/dave/jennifer in the past, and been very happy with it.

If specifically for generating Go code, I would suggest you take a look at Jennifer.

I just spent a few hours writing a crapload of boilerplate code generation code with jennifer, if that helps any.