vanilla-rails-controllers

Rails controller state changes are handled by treating transitions as distinct resources. You extract state logic into dedicated resource controllers and delegate business logic to model methods, following the 37signals resource pattern.

The resource pattern models state transitions as separate controllers. Each transition becomes a resource with create to enter the state and destroy to leave it, ensuring consistent routing and clear separation from business logic.

Routes for Rails state change resources use standard singular or plural resources. You map create actions to enter states and destroy actions to leave them, matching the transition resource to straightforward testability.

Yes, this Rails controller pattern requires no external runtime dependencies beyond Rails itself. It applies across existing controllers, routes, and models by delegating state transitions to well-named model methods.

Extract a state transition into its own Rails controller resource whenever a model needs a state change like close, archive, publish, or assign. This reduces fat controllers and duplicated logic by standardizing the design.