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

IDE0130 cannot be disabled in .editorconfig #75169

Open
RaceRalph opened this issue Sep 19, 2024 · 0 comments
Open

IDE0130 cannot be disabled in .editorconfig #75169

RaceRalph opened this issue Sep 19, 2024 · 0 comments
Labels
Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead

Comments

@RaceRalph
Copy link

Version Used: Visual Studio 17.11.4

Steps to Reproduce:

  1. In a c# project create a namespace which doesn't match the folder structure, e.g. in project Xxx use namespace Xxx in a c# file inside folder Yyy.

  2. In the .editorconfig in SolutionItems (shared by all projects in that solution) add the following lines:

[*.cs]
# IDE0130: Namespace does not match folder structure
dotnet_diagnostic.IDE0130.severity = none
  1. Build the project.

Diagnostic Id:
IDE0130 Namespace "Xxx" does not match folder structure, expected "Xxx.Yyy"

Expected Behavior:
No message for IDE0130 should be issued.

Actual Behavior:
A message is reported:

IDE0130 Namespace "Xxx" does not match folder structure, expected "Xxx.Yyy"

All other messages and warnings whose severity has been set to none in .editorconfig are suppressed, which means that in general the .editorconfig file works. Only the line which disables IDE0130 gets ignored.

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

No branches or pull requests

1 participant