rb:boundaries

Detect Rails boundary violations by scanning the app directory for coupling, business logic in controllers, external calls in model callbacks, and services depending on request context. The analysis identifies misplaced logic and recommends explicit refactors.

Refactoring Rails controllers involves extracting misplaced business logic into dedicated services and converting model callbacks to jobs. This process reduces cross-context coupling and enforces clear service boundaries for better architecture.

Configure Packwerk boundaries by adopting enforce_dependencies and enforce_privacy settings for large codebases. This modular monolith approach isolates packages, restricts unauthorized cross-context calls, and prevents deep structural coupling.

Grape endpoints are fully supported for architectural coupling analysis. The scan detects deep cross-context coupling and improper job arguments within Grape applications, recommending explicit APIs or eventing to fix structural violations.

Improper job arguments often occur when passing complex request context objects instead of IDs to background workers. Detecting this boundary violation recommends passing IDs to jobs, decoupling the worker from the web request lifecycle.

Introduce explicit APIs or eventing in Rails when detecting deep cross-context coupling or external calls within model callbacks. This architectural shift isolates service boundaries, replacing brittle direct calls with structured communication.