README-information is old.

[sassembla]

Now,

var repo = github.getRepo(reponame);

this is, maybe

var repo = github.getRepo(username, reponame);

[mattpass]

The manual also mentions repo.list() - that doesn't seem to be in github.js?

Showing a list of files in a repo would be v useful but I can't see this or any other function to create this list? :/

[michael]

Fixed it.

@mattpass did you test the Gists API? I'm just going to add documentation for it and include it in the 0.7.0 release.

[mattpass]

No, haven't tried it with gists. Will try tomorrow if I get chance.

[mattpass]

Don't forget to remove including jQuery dependency from 'setup' section of README, tis no longer needed.

[michael]

@mattpass can you hop on the #_substance channel in freebase.. got some questions.. (refining the api a bit atm)

[mattpass]

Sorry, don't use that but you're welcome to tweet me @mattpass or email matt@mattpass.com

[michael]

I'll push my changes and you can review.. stripping down the gists api a bit. Btw.. github gists api is really nice... we should cover gists by prose somehow..

[mattpass]

Sure OK, will test the whole gists API in the morning and let you know how it goes.

[michael]

i'm already doing some testing. not sure how far i get.

·····························································
http://substance.io · http://quasipartikel.at
·····························································

On Monday, July 23, 2012 at 3:22 PM, mattpass wrote:

Sure OK, will test the whole gists API in the morning and let you know how it goes.

---

Reply to this email directly or view it on GitHub:
#12 (comment)

[michael]

I stripped down the API a bit... we just need gist.update() I think.. so we don't obscure the native JSON-API which is well designed already.. I tested the stuff already... and extended the docs. Please add what's missing and let me know if you have other questions.

Thanks for helping out with the implementation :)

[mattpass]

Sounds good, but a couple of issues. In the manual it says use
var gist = github().getGist(3165654);
but that should be
var gist = github.getGist(3165654);

The bigger problem though is I don't think fork, delete or update work?

See here I have setup a demo page: http://icecoder.net/github/

Press F12 to get a console up and select gist.read from the dropdown. You get a response back, but not for git.fork or gist.delete?

[sassembla]

thanks a lot!

[mattpass]

Have been testing this a little today. I can read, fork, update & delete gists with basic auth fine. With oAuth I can only read them and can't fork, update or delete? Weird.

May have set up my oAuth incorrectly.

Can someone else confirm actions that involve authentication (such as forking, updating etc) works OK with oAuth here?

[michael]

Make sure you have the OAuth context set correctly it needs to have "gist" (you may revoke the token and get a new one). I was running into that problem yesterday.

[mattpass]

facepalm totally ignored the scope setting so has no context, just public perms. will have another look tomorrow but all 4 functions were working fine with basic auth so should be fine.

[michael]

Just fixed a bunch of other problems... + improved error handling (latest commit) GitHub API is having issues with content type determination... setting this:

xhr.setRequestHeader('Content-Type','application/json');

made it work. Now we store content with special characters again.

Arrr... HTTP sucks

[mattpass]

I thought it was a bit strange the content type was 'application/x-www-form-urlencoded' your previous jQuery AJAX version but I went along with it as I didn't want to break anything for you. Makes more sense now it's 'application/json'.

Also good idea on the improved error handling.

[mattpass]

I also setup a new oAuth token (with gist perms this time) and everything works as expected. Tested all 4 gist commands (read, fork, update & delete) under basic & oAuth, works great. :D