Skip to content

chore: diagnostic logs for dotnet format #336

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.

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

Merged
merged 12 commits into from
May 16, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions scripts/run-docs-tests.ps1
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,20 @@ Pop-Location
if ($FormatAndExecuteTestsAgain) {
Push-Location src
Push-Location FluentAssertions.Analyzers.FluentAssertionAnalyzerDocs
dotnet format analyzers --diagnostics FAA0001 FAA0003 FAA0004 --severity info --verbosity normal

$i = 1;
do {
Write-Host "formatting code... - Iteration $i"
$out = dotnet format analyzers --diagnostics FAA0001 FAA0003 FAA0004 --severity info --verbosity normal 2>&1 | Out-String | Join-String

Write-Host "-------------$i-------------"
Write-Host $out
Write-Host "-------------$i-------------"
Write-Host "output length: $($out.Length)"

$i++
} while ($out.Contains("Unable to fix FAA000"))

Pop-Location
Pop-Location

Expand All @@ -20,4 +33,4 @@ if ($FormatAndExecuteTestsAgain) {
dotnet run verify
Pop-Location
Pop-Location
}
}
Loading