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

Fading option is not activated on already opened files #77319

Closed
raffaeler opened this issue Feb 23, 2025 · 1 comment · Fixed by #77322
Closed

Fading option is not activated on already opened files #77319

raffaeler opened this issue Feb 23, 2025 · 1 comment · Fixed by #77322
Labels

Comments

@raffaeler
Copy link
Contributor

Version Used:
VS2022 17.14.0 Preview 1

This bug is related to the highlighted option which fades out the unused members:
Image

Steps to Reproduce:

  1. Ensure the Fade out unused members is turned on (default)
  2. Open a project and at least one C# file that has unused members. Ensure the unused members are fade out
  3. Turn off the Fade out unused members
  4. The unused members are still fade out
  5. Close the file with unused members
  6. Reopen the file with unused members
  7. Now the unused members are not fade out anymore

Expected Behavior:
I expect that Fade out unused members goes active on the files that are currently open in the editor.

Actual Behavior:
As for the repro, the files that are already open are not fade out.

Reference: #76396 (comment)

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Feb 23, 2025
@CyrusNajmabadi
Copy link
Member

@dibarbet is there a place in Pull Diagnostics where we listen to options changes and use that to issue a diagnostics refresh?

@dotnet-policy-service dotnet-policy-service bot removed the untriaged Issues and PRs which have not yet been triaged by a lead label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants