-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
API Request: Support for "faded" code #20219
Comments
@alexandrudima This might be fitting into semantic highlighting? |
Potentially, that's how it's ultimately implemented under the hood in VS as presentation. Logically, we included in the Roslyn diagnostics API. I'll leave it up to you all to figure out how you'd best expose this to VS Code extensions. |
Any progress on this? |
no progress on this |
@jrieken TypeScript in VS Code now fades unused members--what API do they use to do that? It sounds like that's the same as what's requested here? |
Addressed by #51104 microsoft/language-server-protocol#500 tracks this for the LSP |
This a request from the C# for VS Code extension to provide a way for a diagnostic to present itself as "faded" code. Note that this is orthogonal to the squiggle that appears. It's completely expected that a diagnostic could be "faded" while still appearing with a red, green, or no squiggle.
This is needed to support core editing experiences that we have in Visual Studio for code fixes like "Remove Unnecessary Usings", or "Remove Redundant Cast".
cc @Eilon
The text was updated successfully, but these errors were encountered: