r/webdev • • Oct 18 '18

Angular 7.0.0 released

/r/Angular2/comments/9pbn4f/angular_700_released/
223 Upvotes

148 comments sorted by

View all comments

Show parent comments

0

u/[deleted] Oct 19 '18

[deleted]

27

u/DerpsMcGeeOnDowns Oct 19 '18

5 to 6 required no changes??? Brah... I love Angular but this is factually, demonstrably, and unmistakably false.

0

u/[deleted] Oct 19 '18

[deleted]

2

u/barrybario Oct 19 '18

yep the rxjs changes were breaking for sure

1

u/DerpsMcGeeOnDowns Oct 20 '18

That and completely retooling the CLI, enabling multiple apps in a single workspace via architect, RxJS, the list goes on.

14

u/[deleted] Oct 19 '18

Angular 5 to 6 required no changes.

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.

12

u/Imposter1 Oct 19 '18

Angular 5 to 6 required no changes.

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.

2

u/A-Grey-World Software Developer Oct 19 '18

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/DerpsMcGeeOnDowns Oct 19 '18

5 to 6 required changes for sure. Anyone claiming the opposite doesn’t know. Period.

1

u/itsmoirob Oct 19 '18

5 I think it was is the only really upgrade that broke my work (when they changed to their new .JSON file, plus the httpClientModule stuff)

-3

u/thatgibbyguy Oct 19 '18

the most confusing part of Angular versioning is how so many people struggle with it

Maybe... that's because the versioning is confusing.

18

u/DerpsMcGeeOnDowns Oct 19 '18

Let me break it down for ya:

0.0.1 = bug fixes

0.1.0 = features

1.0.0 = breaking api changes

Simple.

6

u/E2Ehh Oct 19 '18

Everything is confusing if you haven't learned it yet!

https://semver.org/