Ultra Light and Maintainable Rails Wizards
summary
Claims a concrete pattern: one main ActiveRecord plus presenter per step that validates only that part, controller-as-control-flow with RESTful URLs for nested model parts, and no client-side state tricks. Example uses a four steps wizard for EarlyShare, persists each step server-side, and reduces controllers/tests so a rewrite ships in about 7 days where a previous design took a month. Gems mentioned: wicked for stepping; ultralightwizard planned; implementation works and stays maintainable.
AI-written summary · about
chapters (12)
- 0:00Start
- 4:16Basic Info
- 4:28Preview
- 6:12One Controller Per Wizard Step
- 9:25One Action/Presenter Per Wizard Step
- 9:46One Action Presenter Per Wizard Step
- 10:52Session Accumulation
- 13:33Hidden Value Accumulation
- 28:23Routes
- 28:50Step Sub-Models aka Model Parts
- 30:03Projects Controller
- 33:06Step View Template Example
related talks
27mDecouple Your Models with Form Objects
39mExploring Rails anti-patterns
31mWhat Comes After MVC
35mModularizing Rails Monoliths One Bite at a Time
46mRails as a piece of birthday cake
41mOff the Tracks - Challenging the Rails Mindset
38mAll you need is Rails (Engines): Compartmentalising your Monolith
31mIf it bleeds, it leads