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

Duplicate build errors are not collapsed in the error list #70044

Closed
sharwell opened this issue Sep 20, 2023 · 7 comments
Closed

Duplicate build errors are not collapsed in the error list #70044

sharwell opened this issue Sep 20, 2023 · 7 comments
Assignees

Comments

@sharwell
Copy link
Member

Version Used:

  • Analysis scope set to Open Documents via Solution Explorer
  • LSP pull diagnostics enabled

Steps to Reproduce:

  1. Introduce a single build warning in a multi-targeted project
  2. Build the project
  3. Open the document with the build warning
  4. Close the document with the build warning

Expected Behavior:

  • After steps (2), (3), and (4), a single line appears in the error list showing the build warning

Actual Behavior:

  • After step (2), one line appears in the error list for each target of the multi-targeted project. These lines are duplicates of each other.
  • After step (3), the warning collapses to a single line, and the Project column reveals each of the targets where the warning appears
  • After step (4), the warning expands to match the behavior after step (2)
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Analyzers untriaged Issues and PRs which have not yet been triaged by a lead labels Sep 20, 2023
@CyrusNajmabadi
Copy link
Member

@AmadeusW @kayle

@CyrusNajmabadi
Copy link
Member

Note: prior to step 2 this is handled by another team. @AmadeusW @kayle do you know who owns populating the build diagnostics? we likely need to pull them in.

@kayle
Copy link

kayle commented Sep 21, 2023

Looks like Project System
image

The Identifier property needs to be set for diagnostics to be merged:
image

@CyrusNajmabadi
Copy link
Member

@tmeschter do you know who we can pull in here on the project system to fixup build-diagnostics so that they get properly collapsed in VS?

Currently when roslyn is responsible for diagnostics, i presume we do this work. But in the new LSP world, the project system just reports the diagnostics directly through LSP, and it will have to populate this data as well so that the experience is good.

@sharwell could you show images of hte "with/without" pull diagnostics to help motivate this? It would be good to see how bad it is when the diagnostics are duplicated/triplicated/etc. depending on the number of project flavors.

Thanks!

@CyrusNajmabadi
Copy link
Member

@adrianvmsft @lifengl can you look into this for us. We really want to move to LSP pull diagnostics, but diagnostics/error-list is such a critical experience for us, we don't want to regress things in areas like this. Thanks!

@CyrusNajmabadi
Copy link
Member

@arunchndr arunchndr removed the untriaged Issues and PRs which have not yet been triaged by a lead label Oct 2, 2023
@CyrusNajmabadi
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants