End-to-end process for a Modal props API break
WHAT IT TESTS: the full lifecycle of a breaking API change. OUTLINE: justify and design the change, additive rollout with deprecation, major release plus codemod, comms and adoption tracking.
WHAT IT TESTS: whether you can run a breaking change as a process from need to adoption. ANSWER OUTLINE: validate the need and gather input, design the new props API and an RFC, roll out additively so old and new coexist, deprecate the old with warnings, release as a major with a codemod and migration guide, communicate through multiple channels with a timeline, and track adoption before removing the old API. RED FLAG: a sudden hard swap with no RFC, no deprecation overlap, and no migration tooling.
Read the original → interview
- #breaking-changes
- #rfc
- #migration
- #modal
- #versioning
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.