dhh-rails-style

To apply DHH Rails style, enforce RESTful CRUD mappings, fat models, thin controllers, Current attributes, and Turbo/Stimulus frontends. This approach restructures code generation and refactoring requests for maintainable Ruby on Rails applications.

The DHH approach models state as dedicated database records rather than using boolean flags. This means creating specific models like Closure or Goldness to represent state, ensuring cleaner fat models and maintainable Ruby code.

Align Rails controllers with REST by mapping actions directly to resources and preferring new resources over custom actions. This DHH style guidance keeps controllers thin and standardizes interactions across your Ruby codebase.

Yes, DHH Rails style promotes Turbo and Stimulus for modern frontend patterns. This approach builds interactive UIs using a database-backed architecture, avoiding heavy JavaScript frameworks while maintaining request-scoped state with Current attributes.

Yes, DHH Rails style enforces a database-backed approach using Minitest and fixtures. This testing convention aligns with 37signals and Basecamp practices, ensuring reliable Ruby code reviews and refactoring requests.

Use Current attributes in Ruby on Rails to manage request-scoped state, a core DHH style convention. This pattern supports clean fat models and thin controllers by providing a centralized way to access current user or session data.