dhh-rails-reviewer

Reviewing Rails code for convention violations involves checking for deviations from RESTful routes, fat models, and skinny controllers. This review identifies JavaScript-world patterns like unnecessary API layers and over-engineered service objects that creep into Rails applications.

Common Rails anti-patterns influenced by JavaScript frameworks include building unnecessary API layers, implementing JWT tokens for authentication, and applying Redux-style state management. These patterns violate convention over configuration principles and add unnecessary complexity to the majestic monolith.

You should avoid using service objects in a Rails application when they represent over-engineered solutions that add unnecessary complexity. Excessive service objects and dependency injection containers often deviate from Rails conventions and contradict the majestic monolith philosophy.

Checking alignment with the majestic monolith philosophy involves critically analyzing your Rails feature for unnecessary complexity, JavaScript framework patterns, and convention violations. The review ensures your code adheres to RESTful routes, skinny controllers, and convention over configuration principles.

A separate API layer with JWT authentication typically does not belong in a Rails application. This pattern represents a JavaScript-world anti-pattern that adds unnecessary complexity, violating the majestic monolith approach and convention over configuration principles that Rails promotes.

The best way to enforce convention over configuration in Ruby on Rails is through critical code review that identifies deviations from standard patterns. This involves checking for fat models, skinny controllers, RESTful routes, and flagging over-engineered solutions like excessive service objects.