Skip to content

Add @deprecated reasons in lib.dom.d.ts #39514

@mjbvz

Description

@mjbvz

TypeScript Version: 4.0.0-beta

Search Terms

  • @deprecated
  • dom
  • d.ts

Problem

With TypeScript 4.0, we now render use of @deprecated apis. 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 problem

Proposal

Where possible, add @deprecated messages to the dom apis. See the MDN documentation on the deprecated ScriptProcessorNode for example: https://developer.mozilla.org/en-US/docs/Web/API/ScriptProcessorNode

/cc @DanielRosenwasser

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugA bug in TypeScriptDomain: lib.d.tsThe issue relates to the different libraries shipped with TypeScriptRescheduledThis issue was previously scheduled to an earlier milestone

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions