Skip to content
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

doc: clarify fs.read() #14631

Closed
wants to merge 2 commits into from
Closed

doc: clarify fs.read() #14631

wants to merge 2 commits into from

Conversation

Trott
Copy link
Member

@Trott Trott commented Aug 4, 2017

First commit (originally from #14612, closed by OP, authorship of @dcharbonnier retained in the commit, hope this isn't rude of me, this PR is just me trying to get that across the finish line):

doc: clarify the position argument for fs.read

What happen to the file position after a read using a position null or
integer was not clear and you can assume that the cursor of the file
descriptor is updated even if position is an integer.

Fixes: https://github.com/nodejs/node/issues/8397

Second commit (implements a few of the comments from that PR):

doc: improve fs.read() doc text
Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

doc fs

dcharbonnier and others added 2 commits August 4, 2017 09:39
What happen to the file position after a read using a position null or
integer was not clear and you can assume that the cursor of the file
descriptor is updated even if position is an integer.

Fixes: nodejs#8397
@Trott Trott added doc Issues and PRs related to the documentations. fs Issues and PRs related to the fs subsystem / file system. labels Aug 4, 2017
@nodejs-github-bot nodejs-github-bot added doc Issues and PRs related to the documentations. fs Issues and PRs related to the fs subsystem / file system. labels Aug 4, 2017
@Trott
Copy link
Member Author

Trott commented Aug 4, 2017

(If OP wants to re-open #14612, I'm totally happy to close this, or remove their commit so there's no conflict, or whatever.)

@Trott
Copy link
Member Author

Trott commented Aug 7, 2017

Landed in 680285c and 0f325aa

Thanks, @dcharbonnier! 🎉

@Trott Trott closed this Aug 7, 2017
Trott pushed a commit that referenced this pull request Aug 7, 2017
What happen to the file position after a read using a position null or
integer was not clear and you can assume that the cursor of the file
descriptor is updated even if position is an integer.

PR-URL: #14631
Fixes: #8397
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Trott added a commit that referenced this pull request Aug 7, 2017
PR-URL: #14631
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
addaleax pushed a commit that referenced this pull request Aug 10, 2017
What happen to the file position after a read using a position null or
integer was not clear and you can assume that the cursor of the file
descriptor is updated even if position is an integer.

PR-URL: #14631
Fixes: #8397
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
addaleax pushed a commit that referenced this pull request Aug 10, 2017
PR-URL: #14631
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
@addaleax addaleax mentioned this pull request Aug 13, 2017
@MylesBorins
Copy link
Contributor

is this relevant to v6.x?

@Trott
Copy link
Member Author

Trott commented Sep 19, 2017

is this relevant to v6.x?

I believe so. I think it applies to 4.x as well. @nodejs/fs

MylesBorins pushed a commit that referenced this pull request Sep 20, 2017
What happen to the file position after a read using a position null or
integer was not clear and you can assume that the cursor of the file
descriptor is updated even if position is an integer.

PR-URL: #14631
Fixes: #8397
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
MylesBorins pushed a commit that referenced this pull request Sep 20, 2017
PR-URL: #14631
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Sep 20, 2017
@Trott Trott deleted the clarify-fs-read branch January 13, 2022 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations. fs Issues and PRs related to the fs subsystem / file system.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants