I've been considering submitting a PR for godoc to improve content cacheability (namely by adding an Etag header), but I've been hesitant up to this point as I haven't necessarily seen a clear need for (outside of some performance issues on https://godoc.org/ that have now been resolved).
While this wouldn't cause godoc to automatically update its content on changes to your codebase, it would give you an easy way to check for "stale" pages, and invalidate older versions that may be stored in a browser's cache. Is that something people would be interested in? Best regards, Charlton On Thursday, December 20, 2018 at 8:56:11 AM UTC, Sebastien Binet wrote: > > hi there, > > in all my Go-based projects I have a bunch of CI/CD tools that keep me > honest about APIs, tests, coverage and what not. > > but it happens from time to time that I either break an API and/or add a > new field, a new function a new type, etc... > > and it has happened also a few times that one of my user comes back to me > and says the godoc page is stale, missing the new documentation for some > type, etc... > > has somebody written a tool that crawls all the packages and "subpackages" > of a repository and updates the godoc page? > this could be useful as a post-hook when merging into "master" for example. > > cheers, > -s > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
