Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecated property not marked as such #891

Closed
greg0ire opened this issue Apr 30, 2024 · 3 comments
Closed

Deprecated property not marked as such #891

greg0ire opened this issue Apr 30, 2024 · 3 comments

Comments

@greg0ire
Copy link

greg0ire commented Apr 30, 2024

Consider the following piece of code:

interface Hi {
    /** @deprecated */
    stopUsingMe?: string
}
export function foo(): Hi {
    return {
        stopUsingMe: "toto"
    }
}

I would expect a diagnosis letting me know that I shouldn't use stopUsingMe inside foo(), but that does not happen.
I'm using v4.3.3

Note that it works for other elements, for example if I deprecate a function, it's stricken through at every call site.

@rchl
Copy link
Member

rchl commented May 2, 2024

Diagnostics are provided by typescript/tsserver. You should ask about it in the typescript repo instead.

@rchl
Copy link
Member

rchl commented May 2, 2024

This issue looks related: microsoft/TypeScript#45657

@greg0ire
Copy link
Author

greg0ire commented May 2, 2024

It does look related! Thanks 🙏

@greg0ire greg0ire closed this as not planned Won't fix, can't repro, duplicate, stale May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants