1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: drop 'for more details' in deprecations

Browse Source 
The deprecations documentation links to the GitHub issue
tracker in several places. This commit makes the text
around those links consistent.

PR-URL: https://github.com/nodejs/node/pull/28617
Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
This commit is contained in:
cjihrig 2019-07-09 18:57:17 -04:00
parent 2c5716bd72
commit ec5518003f
No known key found for this signature in database
GPG Key ID: 7434390BDBE9B9C5
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/api/deprecations.md
View File

@ -339,7 +339,7 @@ changes:
Type: End-of-Life
Calling an asynchronous function without a callback throws a `TypeError`
in Node.js 10.0.0 onwards. (See <https://github.com/nodejs/node/pull/12562>.)
in Node.js 10.0.0 onwards. See <https://github.com/nodejs/node/pull/12562>.
<a id="DEP0014"></a>
### DEP0014: fs.read legacy String interface
@ -1754,8 +1754,8 @@ changes:
Type: End-of-Life
The AsyncHooks Sensitive API was never documented and had various minor issues.
(See <https://github.com/nodejs/node/issues/15572>.) Use the `AsyncResource`
API instead.
Use the `AsyncResource` API instead. See
<https://github.com/nodejs/node/issues/15572>.
<a id="DEP0086"></a>
### DEP0086: Remove runInAsyncIdScope
@ -1774,8 +1774,7 @@ changes:
Type: End-of-Life
`runInAsyncIdScope` doesn't emit the `'before'` or `'after'` event and can thus
cause a lot of issues. See <https://github.com/nodejs/node/issues/14328> for
more details.
cause a lot of issues. See <https://github.com/nodejs/node/issues/14328>.
<a id="DEP0089"></a>
### DEP0089: require('assert')
@ -1937,7 +1936,7 @@ to unrecoverable errors.
Use [`asyncResource.runInAsyncScope()`][] API instead which provides a much
safer, and more convenient, alternative. See
<https://github.com/nodejs/node/pull/18513> for more details.
<https://github.com/nodejs/node/pull/18513>.
<a id="DEP0099"></a>
### DEP0099: async context-unaware node::MakeCallback C++ APIs