-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Add @deprecated reasons in lib.dom.d.ts #39514
Copy link
Copy link
Closed
microsoft/TypeScript-DOM-lib-generator
#884Closed
Copy link
Labels
BugA bug in TypeScriptA bug in TypeScriptDomain: lib.d.tsThe issue relates to the different libraries shipped with TypeScriptThe issue relates to the different libraries shipped with TypeScriptRescheduledThis issue was previously scheduled to an earlier milestoneThis issue was previously scheduled to an earlier milestone
Milestone
Metadata
Metadata
Assignees
Labels
BugA bug in TypeScriptA bug in TypeScriptDomain: lib.d.tsThe issue relates to the different libraries shipped with TypeScriptThe issue relates to the different libraries shipped with TypeScriptRescheduledThis issue was previously scheduled to an earlier milestoneThis issue was previously scheduled to an earlier milestone
TypeScript Version: 4.0.0-beta
Search Terms
@deprecateddomd.tsProblem
With TypeScript 4.0, we now render use of
@deprecatedapis. The dom apis include many deprecated symbols, but some of these do not include a reason that explains why a given api is deprecated and which API to use instead. This can be frustrating for users who don't want to see a strike through in the code but also don't know how to fix the problemProposal
Where possible, add
@deprecatedmessages to the dom apis. See the MDN documentation on the deprecatedScriptProcessorNodefor example: https://developer.mozilla.org/en-US/docs/Web/API/ScriptProcessorNode/cc @DanielRosenwasser