Fix error in callback signatures#435
Conversation
The functions actually give `null` as the error parameter, and not `undefined`. Without this, `util.promisify` can't be typed correctly on these functions as it expects the callback to receive `Error | null`.
|
/rebuild |
|
LGTM |
|
The build is failing on Windows w/ Node 4:
|
|
ping @mapleeit, could you restart the build for windows/node4? |
done. |
|
Ugh, we're blocked on isaacs/rimraf#195 😅 |
|
I'm afraid so. Can ping me again when it's ready. 😄 |
|
@mapleeit should be good to go now, mind restarting the build again? |
|
Done, waiting for the result. : ) |
|
@LinusU still failed, should we update the version of rimraf in package.json? |
|
Did it 👌 |
|
LGTM. @alexindigo Please take a look if you have time. : ) |
|
ping @alexindigo |
|
@mapleeit Looks good to me, unless it’s a trick question. :) |
|
Both is ok to me, haha. |
|
Would be great if we could get a release cut with this so that we can move forward with sindresorhus/got#849 |
|
We need to ping @alexindigo again 😄 |
|
Thanks 👏 |
The functions actually give
nullas the error parameter, and notundefined.Without this,
util.promisifycan't be typed correctly on these functions as it expects the callback to receiveError | null.