It should be possible to support most or all of the GitHub API v3 using a Patchboard API definition and the various PB clients.
Much work was done here a while back, but the structure of an API Definition has changed, and I removed the support for certain features in the JS client.
https://developer.github.com/v3/
Certain of the GH API resource associations are not hyperlinked (repo.contributors, repo.languages). We'll need to devise a way to specify these associations and generate their URLs client-side. I also recall having introduced an "alias" field in the mappings, but do not recall the reason.
There can be some problems in generating URLs related to the properties available in a resource. This was the reason for the hacky functions found here:
https://github.com/pandastrike/patchboard-examples/blob/master/github/client.coffee#L17-L24
It should be possible to support most or all of the GitHub API v3 using a Patchboard API definition and the various PB clients.
Much work was done here a while back, but the structure of an API Definition has changed, and I removed the support for certain features in the JS client.
https://developer.github.com/v3/
Certain of the GH API resource associations are not hyperlinked (repo.contributors, repo.languages). We'll need to devise a way to specify these associations and generate their URLs client-side. I also recall having introduced an "alias" field in the mappings, but do not recall the reason.
There can be some problems in generating URLs related to the properties available in a resource. This was the reason for the hacky functions found here:
https://github.com/pandastrike/patchboard-examples/blob/master/github/client.coffee#L17-L24