Pattern Consistency Deviation
Detects mixed sync/async naming conventions and service locator anti-patterns introduced inconsistently within the same file.
Why this rule exists
Inconsistency confuses callers. A class with both GetUser and GetOrderAsync forces every caller to remember which is which, and the wrong choice can deadlock.
Code example
+ public Task<User> GetUser(int id) => ...;
+ public Task<Order> GetOrderAsync(int id) => ...;+ public Task<User> GetUserAsync(int id) => ...;
+ public Task<Order> GetOrderAsync(int id) => ...;Configuration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0046": { "enabled": true, "severity": "Info" }
}
}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.
Dependency Injection Safety
Detects DI anti-patterns: service locator usage, direct instantiation of injectable types, and captive dependency violations.
Naming and Contract Alignment
Detects method renames where the new CRUD verb semantically contradicts the old verb, signaling an intent mismatch.
Discussed in
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0046_*.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.