fix(node/fs): position option of fs.read and fs.readSync works the same as Node #2669
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The behavior of
position
option infs.read
andfs.readSync
is different between Deno and Node.This PR fixes the behavior of Deno to be the same as Node's.
Actual Behavior
Node v18.9.0
If
position
is an integer,Ref: https://nodejs.org/api/fs.html#fsreadfd-buffer-offset-length-position-callback
Deno 1.25.3 with [email protected]
If
position
is an integer,Sample code
Execution result in Node
Execution result in Deno
Tests
No applicable test for this issue has been found in the Node test suite. Unit tests have been updated.
Remarks
This issue has been found while implementing compatibility improvements to fs.ReadStream. #2653