Tracking issue for missing documentation of .NET6 CAxxxx rules
Youssef1313 opened this issue ยท 12 comments
TODO
- CA1419 added in dotnet/roslyn-analyzers#5043.
- CA1727
- CA1842 and CA1843 added in dotnet/roslyn-analyzers#4841
- CA1848
- CA2017
- CA2253
- CA2254 added in dotnet/roslyn-analyzers#5244.
- CA2256
- CA2257
- CA2258
Done
-
CA1418 added in dotnet/roslyn-analyzers#4838.
-
CA1839 and CA1840 added in dotnet/roslyn-analyzers#4909
-
CA1841 added in dotnet/roslyn-analyzers#4687. Documentation PR #23887
-
CA1845 added in dotnet/roslyn-analyzers#4764. Documentation PR #24270
-
CA1844 added in dotnet/roslyn-analyzers#4726. Documentation PR #24278
-
CA1846 added in dotnet/roslyn-analyzers#4806. Documentation PR #24325
-
CA1847 added in dotnet/roslyn-analyzers#4908. Documentation PR #23377
-
CA1850 (Documentation PR #26634)
-
CA2018 added in dotnet/roslyn-analyzers#5242.
-
CA2250 added in dotnet/roslyn-analyzers#4864. Documentation PR #24324
-
CA2251 added in dotnet/roslyn-analyzers#5116. Documentation PR #24463.
-
CA2255 added in dotnet/roslyn-analyzers#5347.
See https://github.com/dotnet/roslyn-analyzers/blob/main/src/NetAnalyzers/RulesMissingDocumentation.md.
Tagging @buyaa-n @stephentoub @ryzngard @jkoritzinsky @NewellClark @MeikTranel who implemented these in case any of you wants to open a docs PR.
Thank you so much for creating this doc isssue @Youssef1313! You are always one step ahead of us :-)
Also tagging @jeffhandley as an FYI
Adding @buyaa-n and @carlossanlop for their tracking.
@Youssef1313 can you add #23377 to the CA1847 Rule point? I've reopened the PR a while ago.
Visual Studio 2022 shows CA2254 warnings, but the link is broken? It is also missing in https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/
But if I look in the issue, it should be already merged? "CA2254 added in Enabled logging analyzer on new repo roslyn-analyzers#5244."
@mikeKuester The PR that's merged is that product PR. The docs PR isn't yet created. cc @maryamariyan
@Youssef1313 Ok, it is a little bit strange, that a new analyser is deployed without an explanation. :(
At least from my user perspective.
@Youssef1313 Ok, it is a little bit strange, that a new analyser is deployed without an explanation. :( At least from my user perspective.
Is this analyser live in main or or preview?
It's been live in non-preview VS2022 for a while ๐
I didn't install the VS2022 preview, so it's live since the first stable VS2022 version. (actual 17.0.5)
The issue is probably near to be fixed. See #27885
Yay! ๐