So I recently tried enabling this rule in my entire repo and let an LLM fix it. But instead of properly addressing it all of the time sometimes it would just turn the guard into an if statement. I could force it to use Enum.count_until for this one time fix but I think this check should be expanded so its not lazily fixed by moving the problem.
So I recently tried enabling this rule in my entire repo and let an LLM fix it. But instead of properly addressing it all of the time sometimes it would just turn the guard into an if statement. I could force it to use
Enum.count_untilfor this one time fix but I think this check should be expanded so its not lazily fixed by moving the problem.