Skip to content

doc: order deprecation reasons #27960

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.

Sign up for GitHub

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

Closed
wants to merge 6 commits into from
Closed

doc: order deprecation reasons #27960

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
05f668b
doc: order deprecation reasons
trivikr May 29, 2019
07c4177
doc: suggestion from Trott
trivikr May 30, 2019
6c231f2
doc: uppercase the first letter in list
trivikr May 30, 2019
88c7acf
doc: add any of the following
trivikr Jun 2, 2019
0e5235b
Update doc/api/deprecations.md
trivikr Jun 2, 2019
dd75200
Update doc/api/deprecations.md
trivikr Jun 2, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions doc/api/deprecations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,11 @@
<!--introduced_in=v7.7.0-->
<!-- type=misc -->

Node.js may deprecate APIs when either: (a) use of the API is considered to be
unsafe, (b) an improved alternative API is available, or (c) breaking changes to
the API are expected in a future major release.
Node.js may deprecate APIs for any of the following reasons:

* Use of the API is considered to be unsafe.
* An improved alternative API is available.
* Breaking changes to the API are expected in a future major release.

Node.js utilizes three kinds of Deprecations:

Expand Down