From d511d244f5853e63498ff18f3723b26f7b13ec38 Mon Sep 17 00:00:00 2001 From: Anthony Simmon Date: Fri, 16 Feb 2024 17:50:22 -0500 Subject: [PATCH] Typo --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index aca96ba..74e9584 100644 --- a/README.md +++ b/README.md @@ -52,13 +52,13 @@ From experience, installing the package will result in numerous warnings, the ma Firstly, warnings related to code formatting **can be automatically corrected**. This includes: indentation, unnecessary spaces, empty lines, braces, file-scoped namespaces, unnecessary using directives, etc. Here is the command to execute: ``` -dotnet format --severity warn --diagnostics IDE0001 IDE0004 IDE0005 IDE0007 IDE0009 IDE0011 IDE0055 IDE0161 IDE2000 IDE2001 IDE2002 IDE2003 IDE2004 IDE2005 IDE2006 +dotnet format --diagnostics IDE0001 IDE0004 IDE0005 IDE0007 IDE0009 IDE0011 IDE0055 IDE0161 IDE2000 IDE2001 IDE2002 IDE2003 IDE2004 IDE2005 IDE2006 --verbosity diagnostic ``` Once the pull request is merged, one can then attempt to automatically correct the remaining warnings. Without the noise of formatting warnings, it will be easier to focus on them: ``` -dotnet format --severity warn +dotnet format --severity warn --verbosity diagnostic ``` You can also modify the command to specify the IDs of the analysis rules you wish to automatically correct (if a fix is available). In this way, you avoid manual work, and breaking the correction into several pull requests will increase developers' confidence in the process of adopting new standards.