rb:n1-check

To fix N+1 queries in Rails, scan controllers, serializers, and GraphQL resolvers to locate lazy association loads inside loops, then apply preload, eager_load, or includes strategies to batch the database queries.

N+1 queries in Grape API endpoints are typically caused by serializer-induced repeated loads when associated data is accessed individually for each record, triggering a separate database query per iteration instead of a single batched load.

Bullet and Rails strict_loading both help prevent N+1 query regressions; Bullet detects lazy loads during testing while strict_loading enforces eager loading constraints, and combining them provides robust query optimization checks.

The best way to preload associations in Hotwire screens is to use includes, preload, or eager_load in the controller before rendering the view, ensuring associated data is fetched in a single batch query rather than triggering N+1 database loads.

To detect N+1 queries in GraphQL resolvers and nested API responses, inspect the code paths for repeated single-record database queries triggered by nested object access, then apply preloader APIs or eager_load to batch the association loads.

Use preload for separate batch queries without joins, eager_load when you need to filter by associated records using joins, and includes when you want Active Record to automatically choose between the two based on query conditions.