fix: build warnings in analyzer test project#480
Conversation
Replace deprecated HasCount() with Count(), add ordinal string comparers to Dictionary instances, and configure awaits to not capture the synchronization context.
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #480 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 16 16
Branches 1 1
=========================================
Hits 16 16 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Summary
HasCount()assertion withCount()StringComparer.OrdinaltoDictionary<string, string?>instances (MA0002)ConfigureAwait(false)to awaited calls in test code (MA0004)Test plan
dotnet buildreports 0 warnings, 0 errorsdotnet test tests/NetEvolve.Defaults.Analyzer.Tests.Unit— 55/55 passed