Format Your Elixir Code Now
summary
A code formatter claim: mix format ships with rules that avoid semantic changes, use a 19‑line config and remove trailing commas; the Elixir core conversion shows 425 files changed across 214 PRs, 84 committers, 368 commits in four days, proving it works at scale. A mid‑size app sees churn too (90 files, only 31 passed first run), so enforcement via CI and editor hooks matters — e.g. the check-formatted flag in CI and editor autosave hooks to keep commits green.
AI-written summary · about
chapters (31)
- 0:00Intro
- 2:32Jake Worth
- 3:03Style is subjective
- 3:42Why should I care
- 3:56Where Elixir is headed
- 4:20Agenda
- 4:41A History of Auto Formatting
- 5:03Auto Formatting Definition
- 5:31Lint vs Auto Formatting
- 6:38Where the idea of Auto Formatting came from
- 7:20Auto Formatting solves a modern problem
- 8:30Golang Sogo
- 10:26Whats Happening Now
- 11:12Pull Requests
- 12:17Arguments for and against
- 12:43Argument for
- 18:53Style Concern
- 19:25Julius Caesar
- 21:51Potential benefit of the trailing comma
- 22:12Eagle since law
- 24:26Today I learned
- 26:18Refactoring Project
- 26:34Results
- 28:11PostController
- 30:12Render Function
- 30:52Case Statement
- 31:29Formatter
- 32:22Router
- 33:50Inline Comments
- 35:47Circle CI
- 38:11Conclusion
related talks
11mIntroducing Standard Clojure Style: no fuss code formatting
32mWriting Command Line Applications with Elixir
31mMake your own code formatter in Swift
28mAutomating the Automator
37mCredo - Analysing AST for Fun and Profit
31mCode Style and Violence
01h 01mDoes Your Codebase Spark Joy?
26mCrafting Fully Custom Code Generators