-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Overloads shouldn't gain @deprecated
tags of other overloads in quick info
#49368
Comments
This is working as intended. If we made all of them deprecated, there would be no way to convey that you want someone to use a different overload instead of a different function entirely, so we had to opt for a more granular approach. |
@DanielRosenwasser In that case, the hover text shouldn't show |
@deprecated
tags of other overloads in quick info
Agreed, I think I missed that. Sorry about the incorrect triage. |
I think we can exclude only /**
* comment
*
* @param {string[]} a
*/
export function a(a: string[]): number;
export function a(a: number[]): number;
export function a(a: number[], b: number[]): number; a/*1*/([1], [1])
a/*2*/([1]) |
@a-tarasyuk one of our oldest issues tracks that: #407 I don't think anybody's made a complete proposal, but I have to admit I haven't paid attention in several years. |
@sandersn @DanielRosenwasser I've made a PR (#50904) which filters out the |
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
@deprecated
tag at the top of the first one.api.d.ts
test.ts
@deprecated
when hovering over them.Either the bottom two overloaded functions shouldn't be marked as
@deprecated
when hovering over, or all three functions should be striked-through.The text was updated successfully, but these errors were encountered: