layered-rails

To find Rails architecture violations, analyze the codebase for issues like Current.user in models, request objects in services, or business logic in controllers. This process identifies layer breaches and provides specific refactoring recommendations with code examples.

An anemic model in Rails is a domain model lacking business logic, which harms maintainability by shifting behavior into controllers or services. Analyzing your codebase detects these models and recommends moving domain logic back into the model layer.

Keep Rails controllers thin by ensuring they only handle request routing and responses. During a code review, check that business logic is moved to service objects or domain models, preventing god objects and keeping the controller layer clean.

Use service objects and policies during Rails refactoring to separate business operations from web request handling. Adopt these design patterns when services orchestrate complex operations without mixing layers, ensuring clean separation of concerns.

Yes, you can detect god objects and low-scoring callbacks in a Rails codebase by analyzing it against layered architecture principles. This review identifies code-slicing concerns and provides actionable fixes to refactor bloated classes.

Putting notifications in the Rails domain layer causes architecture issues by coupling external communication to business rules. Analyzing the code identifies these violations and recommends moving notifications out of models to maintain clean separation.