Show deprecation warnings on implementations of a deprecated property

[mjbvz]

🔎 Search Terms

• Deprecated implementation
• Deprecated interface

Related #57584

🕗 Version & Regression Information

Not a regression

⏯ Playground Link

No response

💻 Code

type I = {
    /**
     * @deprecated
     */
    text: string;
};

function f(i: I) { return i; }
f({ text: 'a' });

const a: I = { text: 'a' }
a.text;

🙁 Actual behavior

Currently only the last use of a.text shows as deprecated

🙂 Expected behavior

It would be helpful to also render deprecations for any implementations of I.text too as these are also using the deprecated property

Additional information about the issue

No response

[RyanCavanaugh]

Why is it useful to show a strikethrough in a position where you're required to provide it? You can't delete it the way you would delete a read reference to something

[mjbvz]

Two use case for the VS Code codebase:

• If the deprecated property is optional

• If there's a union type and one of the types is optional. We'd love to support something like this:

type I = {
    /**
     * @deprecated
     */
    text: string;
} | {
    text: { value: string; alias: string };
};

[mathpaquette]

@rbuckton @DanielRosenwasser @andrewbranch could we please assign someone to review this improvement? thank you.

[kylefiegener-gardiant]

Also not seeing any strikethrough when using a deprecated component prop in a TSX file.