Return the repository cache

[drusellers]

GET ~/cache/<owner>/<repo>/issues

What kinds of headers should it return?

Should it return the same api payload as GET /orgs/:org/issues

https://developer.github.com/v3/issues/#list-issues

[dahlbyk]

What kinds of headers should it return?

As close to https://api.github.com/repos/<owner>/<repo>/issues as possible, using sensible min/max where applicable, e.g.

• if we spent any of our GitHub rate limit, return the lowest X-RateLimit-Remaining value
• probably Date and corresponding Etag from the first (newest) page of results

Should it return the same api payload as GET /orgs/:org/issues

Same payload as https://api.github.com/repos/<owner>/<repo>/issues (which should align - array of issue payloads).

[rauhryan]

It would be really awesome if the cache returned all of the issues in one call.

At least I dream that could be a possibility, as well as things like joining in attached branches and things

[rauhryan]

And having queryable unstructured metadata that we could attach, so we could get rid of our weird embedded data hack

[drusellers]

https://github.com/SuaveIO/suave/blob/master/src/Suave/Combinators.fs

How to set headers

[drusellers]

And having queryable unstructured metadata that we could attach, so we could get rid of our weird embedded data hack

We can do it on both the payload and the headers. JSONB + HSTORE FTW

[drusellers]

It would be really awesome if the cache returned all of the issues in one call.

Totally doable