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: remove _Node.js style callback_ #21701

Closed
wants to merge 1 commit into from
Closed

Conversation

Trott
Copy link
Member

@Trott Trott commented Jul 7, 2018

We refer to them only as error-first callbacks in our docs. We don't
call them Node.js style callbacks so let's take this opporutnity to
keep things a bit more concise

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

We refer to them only as _error-first callbacks_ in our docs. We don't
call them _Node.js style callbacks_ so let's take this opporutnity to
keep things a bit more concise
@nodejs-github-bot nodejs-github-bot added doc Issues and PRs related to the documentations. errors Issues and PRs related to JavaScript errors originated in Node.js core. labels Jul 7, 2018
@Trott
Copy link
Member Author

Trott commented Jul 7, 2018

@apapirovski

@Trott Trott added the fast-track PRs that do not need to wait for 48 hours to land. label Jul 7, 2018
@Trott
Copy link
Member Author

Trott commented Jul 7, 2018

👍 to fast-track. kthx

@vsemozhetbyt vsemozhetbyt added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jul 7, 2018
@vsemozhetbyt
Copy link
Contributor

The linter failure seems to be the same notorious outdated plugin issue.

@Trott
Copy link
Member Author

Trott commented Jul 7, 2018

The linter failure seems to be the same notorious outdated plugin issue.

@maclover7 is aware and looking at it. FWIW, if anyone currently involved in Node.js core has the right skill set and would like to help out with our Jenkins stuff, I'm sure the Build WG would be happy to hear about it.

@Trott
Copy link
Member Author

Trott commented Jul 7, 2018

@Trott
Copy link
Member Author

Trott commented Jul 7, 2018

Landed in 01eee53

@Trott Trott closed this Jul 7, 2018
Trott added a commit to Trott/io.js that referenced this pull request Jul 7, 2018
We refer to them only as _error-first callbacks_ in our docs. We don't
call them _Node.js style callbacks_ so let's take this opporutnity to
keep things a bit more concise

PR-URL: nodejs#21701
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
targos pushed a commit that referenced this pull request Jul 8, 2018
We refer to them only as _error-first callbacks_ in our docs. We don't
call them _Node.js style callbacks_ so let's take this opporutnity to
keep things a bit more concise

PR-URL: #21701
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
targos pushed a commit that referenced this pull request Jul 9, 2018
We refer to them only as _error-first callbacks_ in our docs. We don't
call them _Node.js style callbacks_ so let's take this opporutnity to
keep things a bit more concise

PR-URL: #21701
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
@targos targos mentioned this pull request Jul 17, 2018
@Trott Trott deleted the error-first branch January 13, 2022 22:49
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. doc Issues and PRs related to the documentations. errors Issues and PRs related to JavaScript errors originated in Node.js core. fast-track PRs that do not need to wait for 48 hours to land.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants