Applying Code Standards Retroactively
summary
Team retrofits a large TypeScript Angular front end by automating renames, formatting and AST rewrites: uses Node.js file system API to rename .html to .component.html and update imports, AST tools to add semicolons and enforce const/let, clang-format and Angular template parser for HTML, and a custom VS Code extension to move files and update references. A six‑person hackathon converts 600,000 lines of JS to TS in three days using Gent. Changes touch every file, break the git history, and are validated by compiler checks and Jenkins builds.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 1:59Why retroactive refactoring
- 3:44Strategies for enforcing standards
- 6:52Automating code changes
- 9:41Mitigating refactoring risks
- 12:30Advice to avoid future refactoring
- 14:17Handling merge conflicts
- 16:41Q&A session
related talks
47mComputer, refactor my code!
07mAuto maintaining thousands of code demos across multiple framework variations, Stephen Cooper
34mMass Frontend Refactors: Less Stress; More Success
40mRefactoring large JavaScript codebases
25mManage large refactors with JSCodeShift
20mThey see me refactorin'. They hatin'
40mHow To (Semi-)Automate JavaScript Refactoring
21mAutomating Front-End Refactoring