Skip to content

Commit

Permalink
doc: order deprecation reasons
Browse files Browse the repository at this point in the history
PR-URL: #27960
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Yongsheng Zhang <[email protected]>
  • Loading branch information
trivikr authored and BridgeAR committed Jun 17, 2019
1 parent 62de36e commit 9dd4813
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions doc/api/deprecations.md
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

0 comments on commit 9dd4813

Please sign in to comment.