Resolve Errors Straight from the Error Pages
summary
Rails 6 ships actionable errors that put buttons on developer error pages to run fixup code, implemented by adding an ActionSupport::ActionableError module to exceptions, rendering buttons inside ActionDispatch::DebugExceptions, and dispatching them with an ActionableExceptions middleware. An Interceptor API replaces fragile monkey‑patches so middleware and error trackers can observe exceptions cleanly. The plugin pattern mirrors pending migrations: detect the missing setup (Active Storage / Action Mailbox), raise an actionable error and offer an install action; the demo hiccups but the feature is merged.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:14Pain Free Rails
- 2:38Resolve Errors Straight from the Error Pages!
- 8:28Error Handling in Rails
- 8:45Rack Application
- 10:00Rack Middleware
- 10:39Rails Middleware Stack
- 21:11The Interceptor API
- 21:58Application vs Framework Traces
- 23:36Actionable Errors
- 25:37Strategies
- 25:50Middleware Checker
- 26:43Act on Existing Errors
related talks
36mThe Arcane Art of Error Handling
30mRuby on Fails: effective error handling with...
28mFrom Cryptic Error Messages To Rails Contributor
31mActiveSupport and ActiveModel
28mDissecting Rails
42mPowerful Rails Features You Might Not Know
38mRails hurts, because you're using it wrong. Let's fix that
41mOff the Tracks - Challenging the Rails Mindset