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.

Sign up for GitHub

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

Jump to bottom

EditorConfigFiles vs GlobalAnalyzerConfigTypes #41585

Closed
uladz-zubrycki opened this issue Jun 28, 2024 · 1 comment · Fixed by #42385
Closed

EditorConfigFiles vs GlobalAnalyzerConfigTypes #41585

uladz-zubrycki opened this issue Jun 28, 2024 · 1 comment · Fixed by #42385
Assignees
@gewarren
Labels
dotnet-fundamentals/svc in-pr This issue will be closed (fixed) by an active pull request. Pri2 📌 seQUESTered Identifies that an issue has been imported into Quest.

Comments

@uladz-zubrycki
Copy link

uladz-zubrycki commented Jun 28, 2024 •
edited by sequestor bot
Loading

Type of issue

Outdated article

Description

According to dotnet/roslyn#47707 the MSBuild ItemGroup to include global analyzerconfig files into is GlobalAnalyzerConfigFiles now, yet in the current article both EditorConfigFiles and GlobalAnalyzerConfigFiles are used in a few different examples introducing an unnecessary confusion

I'm not sure if EditorConfigFiles is still supported, but would prefer seeing the only option used consistently.

Page URL

https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/configuration-files

Content source URL

https://github.com/dotnet/docs/blob/main/docs/fundamentals/code-analysis/configuration-files.md

Document Version Independent Id

cb44b30a-3fcc-3384-3fcd-1ac2675bf470

Article author

@gewarren

Metadata

  • ID: ddb7b648-6f01-eaeb-1292-4baee5ae0666
  • Service: dotnet-fundamentals

Associated WorkItem - 292102
@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Jun 28, 2024
@gewarren gewarren self-assigned this Jul 9, 2024
@gewarren gewarren added the 🗺️ reQUEST Triggers an issue to be imported into Quest. label Aug 1, 2024
@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label Aug 1, 2024
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Aug 1, 2024
@adegeo adegeo added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Aug 12, 2024
@dotnet-bot dotnet-bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Aug 12, 2024
@gewarren gewarren mentioned this issue Aug 29, 2024
Merged
@dotnet-policy-service dotnet-policy-service bot added the in-pr This issue will be closed (fixed) by an active pull request. label Aug 29, 2024
@uladz-zubrycki
Copy link
Author

Thanks @gewarren

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gewarren gewarren

Labels
dotnet-fundamentals/svc in-pr This issue will be closed (fixed) by an active pull request. Pri2 📌 seQUESTered Identifies that an issue has been imported into Quest.
Projects
No open projects
dotnet/docs August 2024 Sprint
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use consistent global analyzer file setting gewarren/docs
4 participants
@uladz-zubrycki @dotnet-bot @gewarren @adegeo