You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logging out NodeGit objects will make them appear empty. This isn't a fault with NodeGit or your program, it's just how things get logged. If you were to log repo.__proto__ you'd see the prototype object looked up.
Yeah, a LOT of the functionality has been implemented on master, ahead of 0.2.7. We're pushing forward with an 0.3 release as quickly as possible, to get that stuff out in the wild where its safe to use.
Activity
tbranyen commentedon Feb 18, 2015
Logging out NodeGit objects will make them appear empty. This isn't a fault with NodeGit or your program, it's just how things get logged. If you were to log
repo.__proto__you'd see the prototype object looked up.max-mykhailenko commentedon Feb 18, 2015
Any log after https://github.com/nodegit/nodegit/blob/master/examples/status.js#L8 (in git status callback) doesn't run.
tbranyen commentedon Feb 18, 2015
Probably due to an error, if you want to see if an error is logged, change that line to:
max-mykhailenko commentedon Feb 18, 2015
Console is empty anyway
max-mykhailenko commentedon Feb 19, 2015
Find error in catch of
getStatusCode
johnhaley81 commentedon Feb 19, 2015
Is this on
masteror0.2.7?max-mykhailenko commentedon Feb 19, 2015
After
npm install nodegit --save-devI got"nodegit": "^0.2.7"in mypackage.jsonjohnhaley81 commentedon Feb 19, 2015
repo.getStatusis only on master.maxkorp commentedon Feb 19, 2015
Yeah, a LOT of the functionality has been implemented on master, ahead of 0.2.7. We're pushing forward with an 0.3 release as quickly as possible, to get that stuff out in the wild where its safe to use.