-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Clarify "fs.readFile", "fs.appendFile", "fs.writeFile" doc… #7561
Conversation
…umentation regarding closing.
@@ -378,7 +378,9 @@ fs.appendFile('message.txt', 'data to append', 'utf8', callback); | |||
|
|||
Any specified file descriptor has to have been opened for appending. | |||
|
|||
_Note: Specified file descriptors will not be closed automatically._ | |||
_Note: If a file descriptor is specified as the 'file', it will not be closed automatically._ |
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.
Please use backticks instead of single quotes around file
here and in the other notes.
In other words:
`file`
instead of:
'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.
Thanks for the feedback, replaced with the backticks in the new commit.
@@ -378,7 +378,9 @@ fs.appendFile('message.txt', 'data to append', 'utf8', callback); | |||
|
|||
Any specified file descriptor has to have been opened for appending. | |||
|
|||
_Note: Specified file descriptors will not be closed automatically._ | |||
_Note: If a file descriptor is specified as the `file`, it will not be closed automatically._ |
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.
Can you please line wrap at no longer than 80-chars
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.
Wrapped in the follow-up commit.
LGTM |
@@ -1130,7 +1132,9 @@ fs.readFile('/etc/passwd', 'utf8', callback); | |||
|
|||
Any specified file descriptor has to support reading. | |||
|
|||
_Note: Specified file descriptors will not be closed automatically._ | |||
_Note: If a file descriptor is specified as the `file`, it will not be closed | |||
automatically. If a filename is specified as the `file`, internally opened |
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.
…, the internally opened …
?
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.
Fixed in the follow-up commit.
LGTM |
_Note: Specified file descriptors will not be closed automatically._ | ||
_Note: If a file descriptor is specified as the `file`, it will not be closed | ||
automatically. If a filename is specified as the `file`, the internally opened | ||
file descriptor will be closed automatically._ |
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.
If the same text has to be repeated multiple times, wouldn't it be better to have it as a separate section and link it wherever necessary?
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.
It's not such a long text and it didn't bother anyone about the original text. Wouldn't it unnecessarily complicate things? Are there any existing precedents of similar treatment of three-liners?
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.
Btw, while that second sentence is true, I’m not sure it’s actually relevant; that writing to a file based on its name includes opening and closing a file descriptor seems like an implementation detail to me which the user doesn’t need to know anything about.
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.
Fair enough. Do you think that the second sentence should be removed altogether? I'm not entirely sure there is no value in explicitly telling the user that he doesn't need to worry about releasing resources in some of the use cases (as opposed to another documented case when he, indeed, should worry), but if you think that it's already implied in a clear enough way in the first sentence, I'm fine with dropping it.
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’d be pretty fine with dropping it, too. The first sentence seems clear enough to me.
OK, removed the excessive second part. Anything else?.. |
@@ -378,7 +378,8 @@ fs.appendFile('message.txt', 'data to append', 'utf8', callback); | |||
|
|||
Any specified file descriptor has to have been opened for appending. | |||
|
|||
_Note: Specified file descriptors will not be closed automatically._ | |||
_Note: If a file descriptor is specified as the `file`, it will not be closed | |||
automatically._ |
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 think we can remove automatically
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.
It was in the original text. It makes perfect sense. It's just one word and doesn't overload text or can be a source of confusion. Why does it have to be removed?..
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’m +1 on keeping it, too. The file descriptor obviously should be closed at some point, that just doesn’t happen by calling {append,read,write}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.
Does that mean that this PR is finally in a proper shape :)?
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.
That’s what my “LGTM” (= looks good to me) basically says, yes. :) It’s still part of the process of merging PRs that collaborators have the chance to state their opinion on changes, like @thefourtheye did, and discuss them if necessary.
Also, you could do us a favour by squashing the commits here together and formatting the commit message as requested by the CONTRIBUTING.md (that’s also something that can be done by the person landing this PR).
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.
ping @thefourtheye?
Bump to get more feedback on latest suggestion (seriously, how does any documentation change ever gets merged?..) |
Ok, sorry it’s taking so long, I’ll land this by Monday in its current state if there are no objections. |
Landed in beea23a with the commit message modified to fit the contributing.md format. Sorry again this took so long! |
@addaleax np, and thank you! |
Description of change
"fs.readFile", "fs.appendFile", "fs.writeFile" documentation is made less confusing regarding when does the automatic closing of file descriptors occur.