You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the .editorconfig file that's generated in the root of the folder structure to the solution (like a solution-level item).
Open it. Observe that the EditorConfig GUI editor is correctly loaded.
Move the .editorconfig file to e.g. the tools folder, also add it to the solution, and open it. Observe that the EditorConfig GUI editor is NOT loaded.
Repeat the previous but move the .editorconfig file to anywhere in the src folder. Observe that the EditorConfig GUI editor is correctly loaded.
Open the .editorconfig file under the Lombiq.Analyzers project. Observe that the EditorConfig GUI editor is NOT loaded.
Repeat the file-adding process with a .globalconfig file (any file should do the trick, but you can try the file I'm attaching below). Observe that the EditorConfig GUI editor is NOT loaded.
Diagnostic Id: This doesn't seem like an analyzer bug.
Expected Behavior:
The EditorConfig UI is loaded when opening .editorconfig files regardless of where the file is on the file system.
The EditorConfig UI is loaded for .globalconfig files, both named just .globalconfig and Anything.globalconfig. This is necessary if you add analyzer rules to a global AnalyzerConfig, i.e. .globalconfig file, as instructed by the official docs instead of .editorconfig.
Actual Behavior:
The EditorConfig UI is only loaded when the .editorconfig file is put into the root folder, or within the src folder (perhaps because that's where the solution's startup project is).
The EditorConfig UI is NOT loaded for any .globalconfig file.
The text was updated successfully, but these errors were encountered:
Version Used: 4.7.0-3.23416.8 (43b0b05) I'm trying this in Visual Studio v17.7.4.
Steps to Reproduce:
--recurse-submodules
switch)..editorconfig
file that's generated in the root of the folder structure to the solution (like a solution-level item)..editorconfig
file to e.g. thetools
folder, also add it to the solution, and open it. Observe that the EditorConfig GUI editor is NOT loaded..editorconfig
file to anywhere in thesrc
folder. Observe that the EditorConfig GUI editor is correctly loaded..editorconfig
file under theLombiq.Analyzers
project. Observe that the EditorConfig GUI editor is NOT loaded..globalconfig
file (any file should do the trick, but you can try the file I'm attaching below). Observe that the EditorConfig GUI editor is NOT loaded.globalconfig.txt
Seems like almost, but not entirely, the same issue: #53845 But this is not fixed, as indicated by comments by others under that issue too.
Also related: #53120
Diagnostic Id: This doesn't seem like an analyzer bug.
Expected Behavior:
.editorconfig
files regardless of where the file is on the file system..globalconfig
files, both named just.globalconfig
andAnything.globalconfig
. This is necessary if you add analyzer rules to a global AnalyzerConfig, i.e. .globalconfig file, as instructed by the official docs instead of.editorconfig
.Actual Behavior:
.editorconfig
file is put into the root folder, or within thesrc
folder (perhaps because that's where the solution's startup project is)..globalconfig
file.The text was updated successfully, but these errors were encountered: