go-oidc-middleware VS jennifer

You can see the PR here and I attached the logs for the workflow run that did the comparison between the versions: https://github.com/XenitAB/go-oidc-middleware/pull/158

I’ve built a library to try and make it easier to consume these services and their JWTs that works with net/http, mux, chi, gin, echo and fiber if you don’t want to implement the logic of discovery and validation yourself: https://github.com/XenitAB/go-oidc-middleware

Source: https://github.com/XenitAB/go-oidc-middleware/blob/main/internal/oidc/cty.go

You can find the module here: https://github.com/XenitAB/go-oidc-middleware

I’ve been spending some free time building a http middleware to make it easy to validate JWT tokens from OpenID Providers: go-oidc-middleware

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.