dotnet/roslyn
Voir sur GitHubIDE0130 Warning uses Symbol name instead of directory path for new files
Open
#78 837 ouverte le 5 juin 2025
Area-IDEhelp wanted
Métriques du dépôt
- Stars
- (20 414 stars)
- Métriques de merge PR
- (Merge moyen 6j 17h) (256 PRs mergées en 30 j)
Description
Version Used: Microsoft.CodeAnalysis.LanguageServer.win-x64 5.0.0-1.25305.1
Steps to Reproduce:
- Create a default project, seems to apply for anything so,
dotnet new console - Make a directory in it
- Make a new class in it with a namespace
- Observe asap Roslyn raises IDE0130, suggesting the namespace should just be "{File's Name}" instead
- Close editor and shut down LSP
- Re-open, observe the issue has now gone away, seems to only occur on newly made files
See the example pic below:
Diagnostic Id: IDE0130
Expected Behavior: IDE0130 Should use the Directory the file exists diff'd with the "root" directory, to determine the expected namespace to suggest
Actual Behavior: It's instead just suggesting a namespace of the File's name, and that's it, see the example pic below
This could theoretically be the plugin handing an invalid path to Roslyn, but as far as I know this sort of stuff just gets detected by Roslyn on its own? Lemme know if this is instead a bug I should raise over on the plugin side instead, or if there's an easy way I can debug which side the issue is on.