From Cryptic Error Messages To Rails Contributor
summary
Shows a concrete fix: change form_with model default from nil to false so passing nil raises an early, clear error; write a unit test, run bin/test, and open a PR that lands but is later changed to emit a deprecation warning first. Uses troubleshooting tools like api.rubyonrails.org, bundle open ActionView and rails console, inspects server logs, edits source, runs isolated tests, and confirms the change works end-to-end before submitting.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 2:08Contributing to Rails intimidating
- 3:11Documentation fixes
- 4:15Debugging error messages
- 5:38GoRails Discord example
- 7:26Rails naming in forms
- 8:47Recreate issue new app
- 10:11Typo and fail debug
- 12:16Test issue new template
- 13:23Locate form_with in Rails
- 15:31Analyze form_with default
- 16:55Propose nil model fix
- 17:57Test change locally
- 18:38Contribute to Rails source
- 19:40Running tests and identifying failures
- 21:45form_with vs form_for
- 22:49Write tests for change
- 23:53Submit pull request
- 24:36Breaking changes handling
- 25:18Encourage contributions
- 26:54Closing remarks
related talks
40mTricks That Rails Didn't Tell You About
37mPrying Open The Black Box
41mOff the Tracks - Challenging the Rails Mindset
31mRails' Insecure Defaults
26mContributing to Rails? Start with the Gems You Already Use
38mRails hurts, because you're using it wrong. Let's fix that
26mDebugging Rails Itself
25mAmelia Bedelia Learns to Code