Async Void Abuse
Detects public async methods that return void instead of Task, which prevents callers from awaiting and catching exceptions.
Why this rule exists
async void is a fire-and-forget antipattern. Any exception thrown crashes the synchronization context rather than propagating to the caller. Use async void only in event handlers where Task return is impossible.
Code example
+ public async void SaveUserAsync(User user) { await _repo.SaveAsync(user); }+ public async Task SaveUserAsync(User user) { await _repo.SaveAsync(user); }
+ // Only use async void for OnClick, OnChange, event handlers, etc.Configuration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0054": { "enabled": true, "severity": "Warn" }
}
}See Configuration for the full schema.
Related rules
Concurrency and State Risk
Detects async void methods, blocking async calls (.Result, .Wait()), static mutable state, and patterns that introduce deadlock risk.
Error Handling Integrity
Detects swallowed exceptions (empty catch blocks) and exception handling patterns that hide failures from callers and operators.
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0054_*.cs.
Eric Cogen -- Founder, GauntletCI
Twenty years in .NET production. Most of those years, the bugs that hurt me were not the ones tests caught. They were the assumptions I did not know I was making: a removed guard clause, a renamed method that still did the old thing, a catch {} that turned a page into a silent dashboard lie. GauntletCI is the checklist I wish I had run before every commit. It runs the rules I learned the hard way, so you do not have to.