From bf2d5a75f8a7e0e577e84206e4b834c7087cbc13 Mon Sep 17 00:00:00 2001 From: Lucas Holmquist Date: Wed, 10 Jul 2019 12:26:50 -0400 Subject: [PATCH] doc: add a link to the throw-deprecations flag Motivation: On the deprecated api's doc, the --pending-deprecation flag is a clickable link to the command line docs. This makes the --throw-deprecation flag, which is described in the next paragraph also a link to keep things consistent PR-URL: https://github.com/nodejs/node/pull/28625 Reviewed-By: Luigi Pinca Reviewed-By: Richard Lau Reviewed-By: Anna Henningsen Reviewed-By: Colin Ihrig Reviewed-By: Jiawen Geng Reviewed-By: Ruben Bridgewater Reviewed-By: Rich Trott --- doc/api/deprecations.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/api/deprecations.md b/doc/api/deprecations.md index 0ea9bd92a162a4..cad264c6c06705 100644 --- a/doc/api/deprecations.md +++ b/doc/api/deprecations.md @@ -26,7 +26,7 @@ are explicitly labeled as such in the A Runtime deprecation will, by default, generate a process warning that will be printed to `stderr` the first time the deprecated API is used. When the -`--throw-deprecation` command-line flag is used, a Runtime deprecation will +[`--throw-deprecation`][] command-line flag is used, a Runtime deprecation will cause an error to be thrown. An End-of-Life deprecation is used when functionality is or will soon be removed @@ -2493,6 +2493,7 @@ Passing a callback to [`worker.terminate()`][] is deprecated. Use the returned [`--http-parser=legacy`]: cli.html#cli_http_parser_library [`--pending-deprecation`]: cli.html#cli_pending_deprecation +[`--throw-deprecation`]: cli.html#cli_throw_deprecation [`Buffer.allocUnsafeSlow(size)`]: buffer.html#buffer_class_method_buffer_allocunsafeslow_size [`Buffer.from(array)`]: buffer.html#buffer_class_method_buffer_from_array [`Buffer.from(buffer)`]: buffer.html#buffer_class_method_buffer_from_buffer