GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — a couple doc improvements / fixes by Fishrock123 · Pull Request #17702 · nodejs/node

Conversation

@Fishrock123

@Fishrock123 Fishrock123 commented Dec 15, 2017

Copy link
Copy Markdown
Contributor
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

Mostly an edit pass over documentation.md but also some fixes to tty.md, fs.md, and synopsis.md.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@Fishrock123 Fishrock123 added the doc Issues and PRs related to Node.js documentation. label Dec 15, 2017
Trott
Trott reviewed Dec 15, 2017
View reviewed changes
Comment thread doc/api/documentation.md Outdated

@Trott Trott Dec 15, 2017

Copy link
Copy Markdown
Member

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 generally opposed to adding bold text except in extremely compelling situations. We waaaaaaay overuse typographical emphasis to the point that it has become mostly meaningless.

I'm especially opposed to it here because this is jargon a lot of people won't understand. I know you didn't write this text here, but "are not subject to the Node.js Semantic Versioning model" is vague and kind of misleading. There's nothing Node.js-specific about semantic versioning, and it's not clear that it could correctly be called a model or what that means/implies.

This text is redundant anyway. The very first sentence says things plainly: "subject to non-backwards compatible changes, or even removal, in any future release." Maybe dispense with this last jargon-y sentence and (if we must emphasize something) emphasize that text instead?

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@Trott Trott Dec 15, 2017

Copy link
Copy Markdown
Member

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.

^^^^ non-blocking objection, by the way. Just comments.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Trott
Trott reviewed Dec 15, 2017
View reviewed changes
Comment thread doc/api/documentation.md Outdated

@Trott Trott Dec 15, 2017

Copy link
Copy Markdown
Member

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.

(Non-blocking) I'd remove *Note*: here and save it for things that really truly need it. Also remove the **Note**: (note different typography 🙄 ) later in this doc.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@Fishrock123 Fishrock123 Dec 16, 2017

Copy link
Copy Markdown
Contributor Author

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 it worth keeping on that one.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Trott
Trott reviewed Dec 15, 2017
View reviewed changes
Comment thread doc/api/documentation.md Outdated

@Trott Trott Dec 15, 2017

Copy link
Copy Markdown
Member

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.

While in here, some -> Some

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Trott
Trott approved these changes Dec 15, 2017
View reviewed changes

@Trott Trott left a comment

Copy link
Copy Markdown
Member

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 left some nits/opinions, but overall, seems like an improvement whether or not those nits/opinions are accepted. 😆

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
vsemozhetbyt
vsemozhetbyt approved these changes Dec 16, 2017
View reviewed changes
Comment thread doc/api/tty.md Outdated

@vsemozhetbyt vsemozhetbyt Dec 16, 2017

Copy link
Copy Markdown
Contributor

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.

A nit: out of ABC order.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@Fishrock123 Fishrock123 Dec 16, 2017

Copy link
Copy Markdown
Contributor Author

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.

Have we actually been enforcing this? I'm kinda clueless - if we have been generally I'll change it, if not... maybe we should do that separately with linting?

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@vsemozhetbyt vsemozhetbyt Dec 16, 2017 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

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.

Sorry, I thought it was enforced in doc linting or style guide, but it seems I am wrong, I cannot even find PRs that sort references explicitly (I recall there were some). So maybe it is OK as is.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@Fishrock123 Fishrock123 Dec 16, 2017 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor Author

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.

For posterity: these are ordered (pretty sure I got it right) in their order of references.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@Fishrock123
Fishrock123 force-pushed the doc-fixes branch from 45740ca to e463ccd Compare December 16, 2017 18:12
@Fishrock123

Fishrock123 commented Dec 16, 2017 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor Author

Lint CI: Edit, oops, again: https://ci.nodejs.org/job/node-test-linter/14546/

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

Fishrock123 added 4 commits December 18, 2017 10:25
@Fishrock123
doc: improve documentation.md
f2e31eb
Reworded some parts, inter-doc links.

PR-URL: nodejs#17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
@Fishrock123
doc: fix fs.existsSync description
934490b
Also works on directories.

PR-URL: nodejs#17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
@Fishrock123
doc: adjust TTY wording & add inter-doc links
606ff7c
PR-URL: nodejs#17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
@Fishrock123
doc: not all example code can be run without 1:1
ce38c49
PR-URL: nodejs#17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
@Fishrock123
Fishrock123 force-pushed the doc-fixes branch from e463ccd to ce38c49 Compare December 18, 2017 15:26
@Fishrock123
Fishrock123 merged commit ce38c49 into nodejs:master Dec 18, 2017
@Fishrock123
Fishrock123 deleted the doc-fixes branch December 18, 2017 15:38
MylesBorins pushed a commit that referenced this pull request Jan 8, 2018
@Fishrock123 @MylesBorins
doc: improve documentation.md
b83fc9b
Reworded some parts, inter-doc links.

PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jan 8, 2018
@Fishrock123 @MylesBorins
doc: fix fs.existsSync description
07be7fb
Also works on directories.

PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jan 8, 2018
@Fishrock123 @MylesBorins
doc: adjust TTY wording & add inter-doc links
4c3d34e
PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jan 8, 2018
@Fishrock123 @MylesBorins
doc: not all example code can be run without 1:1
d7cf473
PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jan 9, 2018
@Fishrock123 @MylesBorins
doc: improve documentation.md
444362e
Reworded some parts, inter-doc links.

PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jan 9, 2018
@Fishrock123 @MylesBorins
doc: fix fs.existsSync description
d193431
Also works on directories.

PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jan 9, 2018
@Fishrock123 @MylesBorins
doc: adjust TTY wording & add inter-doc links
68722fd
PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jan 9, 2018
@Fishrock123 @MylesBorins
doc: not all example code can be run without 1:1
ecbc70f
PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Jan 10, 2018
v9.4.0 proposal #18069
Merged
boingoing pushed a commit to nodejs/node-chakracore that referenced this pull request Jan 18, 2018
@Fishrock123 @boingoing
doc: improve documentation.md
195da8d
Reworded some parts, inter-doc links.

PR-URL: nodejs/node#17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
boingoing pushed a commit to nodejs/node-chakracore that referenced this pull request Jan 18, 2018
@Fishrock123 @boingoing
doc: fix fs.existsSync description
9f3daf1
Also works on directories.

PR-URL: nodejs/node#17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
boingoing pushed a commit to nodejs/node-chakracore that referenced this pull request Jan 18, 2018
@Fishrock123 @boingoing
doc: adjust TTY wording & add inter-doc links
19b4921
PR-URL: nodejs/node#17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
boingoing pushed a commit to nodejs/node-chakracore that referenced this pull request Jan 18, 2018
@Fishrock123 @boingoing
doc: not all example code can be run without 1:1
03803b8
PR-URL: nodejs/node#17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
@MylesBorins MylesBorins added land-on-v6.x labels Jan 23, 2018
gibfahn pushed a commit that referenced this pull request Jan 24, 2018
@Fishrock123 @gibfahn
doc: improve documentation.md
02af31a
Reworded some parts, inter-doc links.

PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
gibfahn pushed a commit that referenced this pull request Jan 24, 2018
@Fishrock123 @gibfahn
doc: fix fs.existsSync description
0ceed2c
Also works on directories.

PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
gibfahn pushed a commit that referenced this pull request Jan 24, 2018
@Fishrock123 @gibfahn
doc: adjust TTY wording & add inter-doc links
87d504d
PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
gibfahn pushed a commit that referenced this pull request Jan 24, 2018
@Fishrock123 @gibfahn
doc: not all example code can be run without 1:1
98c83c6
PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Jan 24, 2018
v6.13.0 proposal #18342
Merged
MylesBorins pushed a commit that referenced this pull request Feb 11, 2018
@Fishrock123 @MylesBorins
doc: improve documentation.md
81f23e7
Reworded some parts, inter-doc links.

PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 11, 2018
@Fishrock123 @MylesBorins
doc: fix fs.existsSync description
5efcd3d
Also works on directories.

PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 11, 2018
@Fishrock123 @MylesBorins
doc: adjust TTY wording & add inter-doc links
c46c17e
PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 11, 2018
@Fishrock123 @MylesBorins
doc: not all example code can be run without 1:1
6e108a5
PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 12, 2018
@Fishrock123 @MylesBorins
doc: improve documentation.md
de25556
Reworded some parts, inter-doc links.

PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 12, 2018
@Fishrock123 @MylesBorins
doc: fix fs.existsSync description
a10f903
Also works on directories.

PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 12, 2018
@Fishrock123 @MylesBorins
doc: adjust TTY wording & add inter-doc links
e02b563
PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 12, 2018
@Fishrock123 @MylesBorins
doc: not all example code can be run without 1:1
0849b1d
PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 13, 2018
@Fishrock123 @MylesBorins
doc: improve documentation.md
6abd459
Reworded some parts, inter-doc links.

PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 13, 2018
@Fishrock123 @MylesBorins
doc: fix fs.existsSync description
9c8d036
Also works on directories.

PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 13, 2018
@Fishrock123 @MylesBorins
doc: adjust TTY wording & add inter-doc links
c683efb
PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 13, 2018
@Fishrock123 @MylesBorins
doc: not all example code can be run without 1:1
423ef3d
PR-URL: #17702
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Trott Trott Trott approved these changes
+1 more reviewer
@vsemozhetbyt vsemozhetbyt vsemozhetbyt approved these changes
Reviewers whose approvals may not affect merge requirements

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

doc Issues and PRs related to Node.js documentation.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

4 participants

@Fishrock123 @MylesBorins @Trott @vsemozhetbyt
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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.