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: improvements to fs.markdown copy #4486

Closed
wants to merge 1 commit into from

Conversation

jasnell
Copy link
Member

@jasnell jasnell commented Dec 30, 2015

A major reworking of the fs.markdown structure and text.
Moved things around so that they are organized by function,
included additional information so there is less of dependency
on knowledge of the POSIX API.

Other changes:

This one will be difficult to review, and I apologize for that. @nodejs/documentation @bnoordhuis

A major reworking of the fs.markdown structure and text.
Moved things around so that they are organized by function,
included additional information so there is less of dependency
on knowledge of the POSIX API.

Other changes:
* Documents `.path` on `fs.ReadStream` and `fs.WriteStream` per
  nodejs#4368
* Include coverage of the file system encoding issue
* Example enhancements throughout
@jasnell jasnell added doc Issues and PRs related to the documentations. fs Issues and PRs related to the fs subsystem / file system. lts-watch-v4.x and removed lts-watch-v4.x labels Dec 30, 2015
@chrisdickinson
Copy link
Contributor

Hm, it looks like GH is suppressing the diff, which may make it hard to leave comments.

@chrisdickinson
Copy link
Contributor

One note I have off the bat is that the error handling bit at the top might be best handled with a link to the appropriate section of the error handling doc.

@chrisdickinson
Copy link
Contributor

This kind of straddles the line between a topic document and a reference document — ideally we'd split this into a "fs" topic doc and a "fs" reference doc, and crosslink between the ref doc and the topic doc. This way we can address questions like "what is a file descriptor and why would I want to manipulate it?" in the topic doc while providing a concise guide for folks who just want to know how to manipulate fds in Node (and, at a broader level, another topic document can address "how do I avoid race conditions" so that this reference doc doesn't have to.)

Taking on the structural changes necessary is somewhat blocked by getting a resolution on #4244, though.

@sam-github
Copy link
Contributor

@jasnell Is there any way of breaking this up into a couple PRs? I'd like to review, but github won't allow, too many changes.

@chrisdickinson
Copy link
Contributor

A thought: could we open a PR to the nodejs/docs repo containing just this file as a single new addition, and do the editing there?

@jasnell
Copy link
Member Author

jasnell commented Jan 30, 2016

That could work. This one is a beast
On Jan 30, 2016 12:30 AM, "Chris Dickinson" notifications@github.com
wrote:

A thought: could we open a PR to the nodejs/docs repo containing just
this file as a single new addition, and do the editing there?


Reply to this email directly or view it on GitHub
#4486 (comment).

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.

4 participants