3 ms·
Everytime I read something about SemVer, breaking changes, etc, I can't help but think about how well Symfony (the PHP framework) handles this. With Symfony, m
by conradk 11y ago
Everytime I read something about SemVer, breaking changes, etc, I can't help but think about how well Symfony (the PHP framework) handles this.
With Symfony, major version changes are not there to break things or bring in tons of new stuff. Instead, it just removes BC layers for stuff that has previously been working but deprecated (with appropriate deprecation warnings).
This makes it easy to switch to a new major version: simply fix all deprecated calls and upgrade, done. At least that's what I experienced moving a project from Symfony 2.x to Symfony 3.x.
- squeaky-clean 11y agoIt sounds like this is exactly what Facebook plans on doing? > Therefore, we're committed to making it easy for most components and libraries built on top of React to be compatible with two major versions at the same time. We will do this by introducing new APIs before completely removing the old ones, thereby avoiding those cliffs. As long as they provide deprecation warnings for APIs that will be removed in the next version, it'll work exactly like you say.
- danabramov 11y agoAnd, to be clear, this is what React team has been doing all along. When you fixed all deprecation warnings in 0.12, you could update to 0.13. React just moved “0” at the end because it has been used in production for years.