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: fix nits in dgram.md #29761

Closed
wants to merge 1 commit into from
Closed

doc: fix nits in dgram.md #29761

wants to merge 1 commit into from

Conversation

vsemozhetbyt
Copy link
Contributor

@vsemozhetbyt vsemozhetbyt commented Sep 29, 2019

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines
  • Make a section with a history remark a YAML section of the relevant method. Refs: doc: fix nits in dgram.md #29761 (comment)
  • Make a bold line a real heading to be included in the TOC.
  • Add formal return types.
  • Reduce redundancy in a description.
  • Unify link format.
  • Fix ASCII sorting in bottom references.

@nodejs-github-bot nodejs-github-bot added dgram Issues and PRs related to the dgram subsystem / UDP. doc Issues and PRs related to the documentations. labels Sep 29, 2019
doc/api/dgram.md Outdated
#### Change to asynchronous `socket.bind()` behavior

As of Node.js v0.10, [`dgram.Socket#bind()`][] changed to an asynchronous
execution model. Legacy code would use synchronous behavior:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like Node v0.10 might be long ago by now that this can just be a YAML changes: entry (without examples)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a simple way to find a PR URL for YAML with this old change?

Copy link
Contributor Author

@vsemozhetbyt vsemozhetbyt Sep 29, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, is this change also relevant for the next socket.bind(options[, callback]) signature? It was added in v0.11.14, i.e. in the version where the previous signature was already asynchronous, so may be it is not relevant. But I may miss simething.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’d omit it, because that was before the time that Node.js necessarily had PRs for commits :)

332fea5 was the change itself and 7169436 added the docs for that (so, like, ~7 years ago).

Copy link
Contributor Author

@vsemozhetbyt vsemozhetbyt Sep 29, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amended to make it a YAML section for the first (older) signature.

* Make a section with a history remark a YAML section
  of the relevant method.
  Refs: #29761 (comment)
* Make a bold line a real heading to be included in the TOC.
* Add formal return types.
* Reduce redundancy in a description.
* Unify link format.
* Fix ASCII sorting in bottom references.
@Trott
Copy link
Member

Trott commented Sep 29, 2019

@Trott Trott added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Sep 29, 2019
@Trott
Copy link
Member

Trott commented Oct 1, 2019

Landed in ddcd235

@Trott Trott closed this Oct 1, 2019
Trott pushed a commit to Trott/io.js that referenced this pull request Oct 1, 2019
* Make a section with a history remark a YAML section
  of the relevant method.
  Refs: nodejs#29761 (comment)
* Make a bold line a real heading to be included in the TOC.
* Add formal return types.
* Reduce redundancy in a description.
* Unify link format.
* Fix ASCII sorting in bottom references.

PR-URL: nodejs#29761
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Minwoo Jung <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
@vsemozhetbyt vsemozhetbyt deleted the doc-fix-nits-dgram branch October 2, 2019 01:19
BridgeAR pushed a commit that referenced this pull request Oct 9, 2019
* Make a section with a history remark a YAML section
  of the relevant method.
  Refs: #29761 (comment)
* Make a bold line a real heading to be included in the TOC.
* Add formal return types.
* Reduce redundancy in a description.
* Unify link format.
* Fix ASCII sorting in bottom references.

PR-URL: #29761
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Minwoo Jung <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
@BridgeAR BridgeAR mentioned this pull request Oct 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. dgram Issues and PRs related to the dgram subsystem / UDP. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants