Dependency Injection Safety
Detects DI anti-patterns: service locator usage, direct instantiation of injectable types, and captive dependency violations.
Why this rule exists
Service locator and captive dependencies make tests harder, lifetimes unpredictable, and refactors expensive. The cost of fixing DI patterns grows superlinearly with codebase size.
Code example
+ public class OrderService
+ {
+ private readonly IRepo _repo = ServiceLocator.Get<IRepo>();
+ }+ public class OrderService
+ {
+ private readonly IRepo _repo;
+ public OrderService(IRepo repo) => _repo = repo;
+ }Configuration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0038": { "enabled": true, "severity": "Warn" }
}
}See Configuration for the full schema.
Related rules
Architecture Layer Guard
Checks added using directives against configured forbidden import pairs, enforcing architectural boundaries at commit time.
Complexity Control
Detects over-engineering: single-use interfaces, abstract classes without abstract members, and unnecessary indirection added in the diff.
Pattern Consistency Deviation
Detects mixed sync/async naming conventions and service locator anti-patterns introduced inconsistently within the same file.
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0038_*.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.