-
Notifications
You must be signed in to change notification settings - Fork 779
Update fs promise shims to support latest Node functions #747
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Sort array to match Node docs
| it('returns an object', () => { | ||
| return fs.writev(TEST_FD, TEST_DATA, 0) | ||
| .then(({ bytesWritten, buffers }) => { | ||
| assert.strictEqual(bytesWritten, SIZE, 'bytesWritten is correct') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe the message should be the opposite, something like bytesWritten is incorrect since that is used as the message for AssertionError if the values are not strictly equal. It is the same for other assertion messages in other tests down below.
https://nodejs.org/api/assert.html#assert_assert_strictequal_actual_expected_message
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, perhaps; I don't think it really matters, the main point is to clearly identify which assertion is throwing if you have an error. In any case, these are simply copied from tests earlier in the file, so if we want to fix this, it should be in a separate PR that fixes the entire file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks @RyanZim!
Added:
fs.writevfs.opendir