statigz VS swaggerui

I've made an http file server to serve pre-compressed or decompressed files out of embedded fs based on Accept-Encoding header: https://github.com/vearutop/statigz.

I thought this approach can work well for Go embedded files too and implemented github.com/vearutop/statigz: a file server that can serve compressed version of an asset if it is available in embedded file system.

I'm excited with this new feature, though I felt a bit of friction in the case of serving compressed assets with http. I like how such problem in solved in http://nginx.org/en/docs/http/ngx_http_gzip_static_module.html, so I've implemented somewhat similar approach for Go 1.16 embedded files: https://github.com/vearutop/statigz, hope it will be helpful.

I have been playing with this functionality in my library, which currently just turns the header off. Haven't used swaggo/swag before, but it looks like they bundle the UI file assets into a separate package that embeds them using another tool and then they generate a handler for you.

Have a look at https://github.com/flowchartsman/swaggerui or one of the forks.

I would probably put my embed and generate directives in the same file for convenience, then I would write a package main file that does your minification work(if you can). Take a look at what I did here. It’s actually a full binary to download the code, and go generate will call it. In your case, this would be your minifier. You would need to make sure you call “go generate” before “go build” if you’ve made any changes to code that might need minified. Mage might be a good option to help you with this, since, unlike the embed directive, generate directives must be manually called.