-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
Add DiagnosticTag.Deprecated #56694
Comments
@jrieken I would be interested in helping out here with this and perhaps even #50972. Without a lot of context, I assume this issue is specifically to add a new enum member here: Line 4274 in 03e1318
I could open a PR that adds a edit: Looks like more applicable location would be |
Yes, |
Thanks, I'll work on that today.
…On Mon, Jul 22, 2019, 4:20 AM Johannes Rieken ***@***.***> wrote:
Yes, vscode.proposed.d.ts is the way to go. Find your way along
usages/implementations of Unnecessary
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#56694?email_source=notifications&email_token=AAEJU24QUT7XLYJZOXNO6HDQAV3W5A5CNFSM4FQG7EU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2PJ5VI#issuecomment-513711829>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEJU22RQDK2SGJJDUVR5GDQAV3W5ANCNFSM4FQG7EUQ>
.
|
feat(Diagnostics): Add proposed DiagnosticTag.Deprecated enum member
Leaving this open so that we discuss this in the API sync |
API has been finalised. |
Now that
DiagnosticTag
has been added to the API, I would like to support the proposal from #51104 to use it for tagging deprecated items.I figure the associated styling might be a strikethrough as proposed in #50972 but you guys can work that out separately.
The text was updated successfully, but these errors were encountered: