This looks promising. In the past I've largely defaulted to calling the REST API directly instead of relying on wrappers - primarily since using a wrapper has basically meant looking up 2 sets of documentation (1 for the REST API itself, and again for the wrapper).
IIRC I had the same frustration the last time I attempted to use Octokit (~5 months ago). GitHub maintaining it directly may well alleviate the pain points I experienced. It would help, for instance, to have the wrapper documentation run parallel with that of the REST API itself.
Comments
This looks promising. In the past I've largely defaulted to calling the REST API directly instead of relying on wrappers - primarily since using a wrapper has basically meant looking up 2 sets of documentation (1 for the REST API itself, and again for the wrapper).
IIRC I had the same frustration the last time I attempted to use Octokit (~5 months ago). GitHub maintaining it directly may well alleviate the pain points I experienced. It would help, for instance, to have the wrapper documentation run parallel with that of the REST API itself.