dotnet/roslyn

Configure or supress issue adds editorconfig file link to different project

Open

#40,955 opened on Jan 14, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (4,257 forks)batch import
Area-IDEBugFeature - Editor ConfigIDE-CodeStylehelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

Version Used: VS Win 16.4.2

Steps to Reproduce:

  1. Create a solution with two .NET Framework class libraries called ProjectA and ProjectB.

  2. In Class1.cs of ProjectB add some code inside a Class1 constructor:

    public Class1() { int abc = 0; }

  3. Right click abc and select Quick Actions and Refactorings - Configure or Suppress issues - Configure CS0219 severity - Error.

Expected Behavior:

.editorconfig file link is added to ProjectB.

Actual Behavior:

.editorconfig file link is added to ProjectA.

Not sure if this is by design. It was confusing to me since I was expecting it to be added to the same project where the Class1.cs file was being worked on.

Contributor guide

Research direction
Investigate the logic in the Roslyn codebase (likely in the Features or Workspaces layer) that determines which project the .editorconfig file link is added to when triggering the 'Configure or Suppress issues' action. Trace the code path from the Quick Actions menu to the project selection mechanism, focusing on how the current project context is obtained and why it might incorrectly select a different project.
Tech stack
csharp
Domain
backenddeveloper experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#.NETVisual Studio
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65