Skip to content

Conversation

@trivikr
Copy link
Member

Checklist

@ZYSzysZYSzys added doc Issues and PRs related to the documentations. deprecations Issues and PRs related to deprecations. labels May 30, 2019
@Trott
Copy link
Member

Potentially-unpopular opinion: All of this text can be deleted. It lists the reasons any platform might deprecate an API. Nothing in there is specific or peculiar to Node.js. And it's not clear that it's a comprehensive list. We don't need to list why we deprecate when those reasons are the same as every other platform. We can go right into the different kinds of deprecations.

@Trott
Copy link
Member

One potential problem with this change: The current wording (mostly) makes it clear that any one of the three possibilities is enough to deprecate. This new format might lead one to think that all three things must be true.

(Another argument for just deleting it!)

@Trott
Copy link
Member

Trott commented May 30, 2019

Lastly: All my comments here are non-blocking. There's always going to be room for improvement. Docs! Amirite?

Copy link
Member

@TrottTrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with punctuation nits.

@Trott
Copy link
Member

Trott commented Jun 2, 2019

@Trott
Copy link
Member

Trott commented Jun 2, 2019

@trivikrtrivikr added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jun 3, 2019
@trivikrtrivikr self-assigned this Jun 3, 2019
@trivikrtrivikrforce-pushed the deprecation-reasons branch from 00abf78 to dd75200CompareJune 3, 2019 19:30
@trivikr
Copy link
MemberAuthor

@trivikr
Copy link
MemberAuthor

ping @Trott@ZYSzys for review post rebase

Copy link
Member

@TrottTrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with or without my remaining suggestion applied

@trivikr
Copy link
MemberAuthor

Landed in 5c61c5d

@trivikrtrivikr closed this Jun 6, 2019
@trivikrtrivikr deleted the deprecation-reasons branch June 6, 2019 05:51
trivikr added a commit to trivikr/node that referenced this pull request Jun 6, 2019
PR-URL: nodejs#27960 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Yongsheng Zhang <[email protected]>
BridgeAR pushed a commit that referenced this pull request Jun 17, 2019
PR-URL: #27960 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Yongsheng Zhang <[email protected]>
@BridgeARBridgeAR mentioned this pull request Jun 17, 2019
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.deprecationsIssues and PRs related to deprecations.docIssues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@trivikr@Trott@ZYSzys