Skip to content

test: add ConfigureAwait guardrail + re-enable dangerous analyzer rules#427

Merged
rygel merged 1 commit intodevelopfrom
test/configureawait-guard
Mar 22, 2026
Merged

test: add ConfigureAwait guardrail + re-enable dangerous analyzer rules#427
rygel merged 1 commit intodevelopfrom
test/configureawait-guard

Conversation

@rygel
Copy link
Copy Markdown
Owner

@rygel rygel commented Mar 22, 2026

Summary

Prevents the beta.18 regression from happening again.

  • New test: scans all WPF code-behind for ConfigureAwait(false)
  • Re-enabled MA0004 (ConfigureAwait) and VSTHRD110 (missing await) in .editorconfig
  • Both were globally suppressed with severity=none, hiding real bugs

NOTE: Depends on PR #426 being merged first (fixes the actual ConfigureAwait(false) on develop).

Test plan

🤖 Generated with Claude Code

Added ConfigureAwaitGuardrailTests that scans all WPF code-behind files
for ConfigureAwait(false). Would have caught the beta.18 regression.

Re-enabled in .editorconfig (were globally suppressed):
- MA0004: ConfigureAwait warnings
- VSTHRD110: missing await on async calls

31 rules were globally suppressed. The dangerous ones (threading,
async, culture) should not be suppressed — they catch real bugs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@rygel rygel merged commit d19c9cb into develop Mar 22, 2026
16 checks passed
@rygel rygel deleted the test/configureawait-guard branch March 22, 2026 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants