doc: wrap links in <>
This fixes links that were broken due to inclusion of the trailing dot. Also simplifies a pair of occurances of [](). PR-URL: https://github.com/nodejs/node/pull/23359 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
This commit is contained in:
parent
98afca92a9
commit
8d29569368
@ -334,7 +334,7 @@ changes:
|
|||||||
Type: End-of-Life
|
Type: End-of-Life
|
||||||
|
|
||||||
Calling an asynchronous function without a callback throws a `TypeError`
|
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>
|
<a id="DEP0014"></a>
|
||||||
### DEP0014: fs.read legacy String interface
|
### DEP0014: fs.read legacy String interface
|
||||||
@ -1717,7 +1717,7 @@ changes:
|
|||||||
Type: End-of-Life
|
Type: End-of-Life
|
||||||
|
|
||||||
The AsyncHooks Sensitive API was never documented and had various minor issues.
|
The AsyncHooks Sensitive API was never documented and had various minor issues.
|
||||||
(See https://github.com/nodejs/node/issues/15572.) Use the `AsyncResource`
|
(See <https://github.com/nodejs/node/issues/15572>.) Use the `AsyncResource`
|
||||||
API instead.
|
API instead.
|
||||||
|
|
||||||
<a id="DEP0086"></a>
|
<a id="DEP0086"></a>
|
||||||
@ -1737,8 +1737,8 @@ changes:
|
|||||||
Type: End-of-Life
|
Type: End-of-Life
|
||||||
|
|
||||||
`runInAsyncIdScope` doesn't emit the `'before'` or `'after'` event and can thus
|
`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
|
cause a lot of issues. See <https://github.com/nodejs/node/issues/14328> for
|
||||||
details.
|
more details.
|
||||||
|
|
||||||
<a id="DEP0089"></a>
|
<a id="DEP0089"></a>
|
||||||
### DEP0089: require('assert')
|
### DEP0089: require('assert')
|
||||||
@ -1897,7 +1897,7 @@ to unrecoverable errors.
|
|||||||
|
|
||||||
Use [`asyncResource.runInAsyncScope()`][] API instead which provides a much
|
Use [`asyncResource.runInAsyncScope()`][] API instead which provides a much
|
||||||
safer, and more convenient, alternative. See
|
safer, and more convenient, alternative. See
|
||||||
https://github.com/nodejs/node/pull/18513 for more details.
|
<https://github.com/nodejs/node/pull/18513> for more details.
|
||||||
|
|
||||||
<a id="DEP0099"></a>
|
<a id="DEP0099"></a>
|
||||||
### DEP0099: async context-unaware node::MakeCallback C++ APIs
|
### DEP0099: async context-unaware node::MakeCallback C++ APIs
|
||||||
|
@ -619,10 +619,10 @@ possible to connect to a long-running Node.js process without restarting it.
|
|||||||
|
|
||||||
For an example of running a "full-featured" (`terminal`) REPL over
|
For an example of running a "full-featured" (`terminal`) REPL over
|
||||||
a `net.Server` and `net.Socket` instance, see:
|
a `net.Server` and `net.Socket` instance, see:
|
||||||
[https://gist.github.com/TooTallNate/2209310](https://gist.github.com/TooTallNate/2209310).
|
<https://gist.github.com/TooTallNate/2209310>.
|
||||||
|
|
||||||
For an example of running a REPL instance over [curl(1)][], see:
|
For an example of running a REPL instance over [curl(1)][], see:
|
||||||
[https://gist.github.com/TooTallNate/2053342](https://gist.github.com/TooTallNate/2053342).
|
<https://gist.github.com/TooTallNate/2053342>.
|
||||||
|
|
||||||
[`'uncaughtException'`]: process.html#process_event_uncaughtexception
|
[`'uncaughtException'`]: process.html#process_event_uncaughtexception
|
||||||
[`--experimental-repl-await`]: cli.html#cli_experimental_repl_await
|
[`--experimental-repl-await`]: cli.html#cli_experimental_repl_await
|
||||||
|
@ -566,7 +566,7 @@ field which always contains the value `'TLSv1/SSLv3'`.
|
|||||||
For example: `{ name: 'AES256-SHA', version: 'TLSv1/SSLv3' }`.
|
For example: `{ name: 'AES256-SHA', version: 'TLSv1/SSLv3' }`.
|
||||||
|
|
||||||
See `SSL_CIPHER_get_name()` in
|
See `SSL_CIPHER_get_name()` in
|
||||||
https://www.openssl.org/docs/man1.1.0/ssl/SSL_CIPHER_get_name.html for more
|
<https://www.openssl.org/docs/man1.1.0/ssl/SSL_CIPHER_get_name.html> for more
|
||||||
information.
|
information.
|
||||||
|
|
||||||
### tlsSocket.getEphemeralKeyInfo()
|
### tlsSocket.getEphemeralKeyInfo()
|
||||||
@ -683,7 +683,7 @@ Example responses include:
|
|||||||
* `TLSv1.2`
|
* `TLSv1.2`
|
||||||
* `unknown`
|
* `unknown`
|
||||||
|
|
||||||
See https://www.openssl.org/docs/man1.1.0/ssl/SSL_get_version.html for more
|
See <https://www.openssl.org/docs/man1.1.0/ssl/SSL_get_version.html> for more
|
||||||
information.
|
information.
|
||||||
|
|
||||||
### tlsSocket.getSession()
|
### tlsSocket.getSession()
|
||||||
|
Loading…
x
Reference in New Issue
Block a user