So they just aren't using semantic versioning? Major version upgrades should be breaking. If the changes don't break the API then it should just be a minor version upgrade.
5 to 6 was a nightmare but that was mostly due to rxjs going from 5 to 6 and the auto update too not working very well on our codebase. We also didn't want to leave the rxjs compat lib in there.
Besides that, yeah I agree, it's been pretty smooth upgrades the whole way through.
Depends if you're using the feature that breaks. 5 - 6 was a massive breaking change for me because I used a load of the RX stuff. I think the poster must have had some changes because RX is pretty integral into Angular - but if he didn't, then he might have had no refactoring. Maybe the auto update tool worked for him and he's forgotten!
It's still a breaking change to the API though, he's just not using that particular change.
Hell, updating to the latest version of TypeScript will be technically a breaking change, but very unlikely to actually impact anyone.
The animation system was changed, a breaking change. I'm guessing a lot of people's applications don't use Animations and they never needed to care. Still a breaking change.
0
u/[deleted] Oct 19 '18
[deleted]