From e20473794969096bec7ad9213e3afdbcdb32ff85 Mon Sep 17 00:00:00 2001 From: James Groom Date: Thu, 16 Mar 2023 10:47:51 +1000 Subject: [PATCH] Updated Roslyn Analyzers (third party) (markdown) --- Roslyn-Analyzers-(third-party).md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Roslyn-Analyzers-(third-party).md b/Roslyn-Analyzers-(third-party).md index 67b30bf..bb36a39 100644 --- a/Roslyn-Analyzers-(third-party).md +++ b/Roslyn-Analyzers-(third-party).md @@ -24,7 +24,7 @@ As a reminder, the project files' include graph looks like: `/Common.props` enables the .NET Analyzers and StyleCop, and imports BizHawk.Analyzer and some third-party Analyzers. You can tell the assembly references are working if `;;` is flagged with "MA0037: Remove empty statement". -You can tell the ruleset reference is working if the above is true but the output isn't flooded with other warnings like "MEN002: Line must be no longer than 160 characters". -Similarly, you can tell the StyleCop config reference is working if the output isn't flooded with other warnings like "SA1600: Elements should be documented". +You can tell the ruleset reference is working if that was flagged but the output isn't flooded with other warnings, such as "MEN002: Line must be no longer than 160 characters". +Similarly, you can tell the StyleCop config reference is working if the output isn't flooded with warnings such as "SA1600: Elements should be documented". > Note: `/src/MainSlnCommon.props` *disables* Analyzers unless `-p:RunAnalyzersDuringBuild=true` is passed to `dotnet` / the build script. \ No newline at end of file