doc: remove "is recommended from crypto legacy API text · nodejs/node@a01011b · GitHub

nodejs / node Public

• Notifications You must be signed in to change notification settings
• Fork 36.6k
• Star 120k

• Code
• Issues 639
• Pull requests 566
• Actions
• Projects
• Security and quality
• Insights

Additional navigation options

Commit a01011b

Browse filesBrowse the repository at this point in the historyBrowse files

Trott

authored and

BethGriggs

committed

doc: remove "is recommended from crypto legacy API text

The text for the legacy API sends mixed signals. It's legacy, but still supported, so not deprecated, but not recommended. Let's begin to clarify this by removing "not recommended". If we want to not-recommend it, let's doc-deprecate it properly, or at least include an explanation as to why it's not recommended. PR-URL: #34697 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ujjwal Sharma <ryzokuken@disroot.org> Reviewed-By: Tobias Nießen <tniessen@tnie.de>

1 parent 7a13e01 commit a01011b
Copy full SHA for a01011b

1 file changed

+2-3Lines changed: 2 additions & 3 deletions

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

• doc/api
  • crypto.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

‎doc/api/crypto.md‎

Copy file name to clipboardExpand all lines: doc/api/crypto.md

+2-3Lines changed: 2 additions & 3 deletions

• Display the source diff
• Display the rich diff

Original file line number	Diff line number	Diff line change
@@ -106,9 +106,8 @@ console.log(Certificate.verifySpkac(Buffer.from(spkac)));
106	106
107	107	### Legacy API
108	108
109		- As a still supported legacy interface, it is possible (but not recommended) to
110		- create new instances of the `crypto.Certificate` class as illustrated in the
111		- examples below.
	109	+ As a still supported legacy interface, it is possible to create new instances of
	110	+ the `crypto.Certificate` class as illustrated in the examples below.
112	111
113	112	#### `new crypto.Certificate()`
114	113

0 commit comments

Comments

0 (0)