I saw your tweet about this this morning, and I instantly thought... You expose the data for all Go issues locally for fast access, and if I just implement the issues.Service interface on top of your issuemirror API, then you could view all those issues locally in browser, even when offline.
(/cc @willnorris I've showed you those Go packages without context, but this is a more practical application of them :D)
Instead of more exciting things, I spent some effort in the past cleaning up some of the components to serve assets like Octicons, etc., locally, instead of https://cdnjs.cloudflare.com/ or the like, and used vfsgen to embed local assets like templates. Primarily because I wanted to make use of HTTP/2 for them, to avoid flash of unstyled content, and have a static Go binary with no external dependencies. The side benefit of doing that work is that everything can load even when offline!
So, without further ado, here's a little go-gettable command I wrote that takes in the issues via the API you expose, implements a simple issues.Service wrapper on top, and serves those so you can view them in browser locally or offline.
Hey @bradfitz,
I saw your tweet about this this morning, and I instantly thought... You expose the data for all Go issues locally for fast access, and if I just implement the
issues.Service
interface on top of your issuemirror API, then you could view all those issues locally in browser, even when offline.(/cc @willnorris I've showed you those Go packages without context, but this is a more practical application of them :D)
Instead of more exciting things, I spent some effort in the past cleaning up some of the components to serve assets like Octicons, etc., locally, instead of https://cdnjs.cloudflare.com/ or the like, and used vfsgen to embed local assets like templates. Primarily because I wanted to make use of HTTP/2 for them, to avoid flash of unstyled content, and have a static Go binary with no external dependencies. The side benefit of doing that work is that everything can load even when offline!
So, without further ado, here's a little go-gettable command I wrote that takes in the issues via the API you expose, implements a simple
issues.Service
wrapper on top, and serves those so you can view them in browser locally or offline.Video Demo
https://www.youtube.com/watch?v=_JN4lMW1dcs
Screenshots
Let me know what you think, I welcome feedback.