On the road to Angular 4: Beta.5

  • The reason behind the decision to drop the version suffix (unless you are talking about “something very specific in a given release”) is that as they are releasing more and more versions, “it’s going to be super confusing for everybody.”
  • The beta phase officially began in mid-December 2016 and has rapidly gone through six beta versions (beta.5 was released on January 25).
  • function myTest(injector: Injector) { var foo = injector.get(Foo); // This line used to work since `foo` used to be `any` before this // change, it will now be `Foo`, and `Foo` does not have `setUpMock()`. // The fix is to downcast: `injector.get(Foo) as MockFoo`.
  • The sixth beta version consists of 11 bug fixes and eight features.
  • Igor also encouraged Angular users to stop using the version suffix and call it (just) “Angular” instead.

Now that the countdown for the release of Angular 4 has begun, it’s time to bring everything under one roof.

@Addstones: On the road to Angular 4: Beta.5 via @JAXenterCOM #Angularjs #Tech #development

Thanks to Semantic Versioning, everything about Angular seems to be set in stone these days: it indicates that “version numbers are meaningful and that patch releases will not change the functionality, minor releases will contain only additive changes, and breaking changes are reserved for major releases,” as Igor Minar, Angular Team Lead at Google, announced in his keynote at  NG-BE, Belgium’s first Angular conference. 

The beta phase officially began in mid-December 2016 and has rapidly gone through six beta versions (beta.5 was released on January 25). The first release candidate is expected to appear on February 8, so the wait is almost over.

But let’s leave the future alone for a second and focus on Beta.5.

The sixth beta version consists of 11 bug fixes and eight features. There’s also a breaking change:

class Foo {} class MockFoo extends Foo { setupMock(); } var PROVIDERS = [ {provide: Foo, useClass: MockFoo} ]; … function myTest(injector: Injector) { var foo = injector.get(Foo); // This line used to work since `foo` used to be `any` before this // change, it will now be `Foo`, and `Foo` does not have `setUpMock()`. // The fix is to downcast: `injector.get(Foo) as MockFoo`. foo.setUpMock(); }

Let’s not forget Angular 2, though. 2.4.5 brings four bug fixes:

Check out the entire thread here.

SEE ALSO: Move over 3 — Angular 4 is the next version

“The change is happening”

Igor emphasized that all the future releases will be introduced with minimal breaking changes. However, he explained that the reason why the Angular team needs these breaking changes is just like in the case of TypeScript: “We can’t be stuck on version 1.8, we’re just going to be obsolete soon. We need to keep evolving with the rest of the ecosystem, with the web. If we find that some APIs that we have in Angular are not ergonomic, we need to figure out a way to make them ergonomic but do it in a way that is not going to break the ecosystem.”

Igor also encouraged Angular users to stop using the version suffix and call it (just) “Angular” instead. The reason behind the decision to drop the version suffix (unless you are talking about “something very specific in a given release”) is that as they are releasing more and more versions, “it’s going to be super confusing for everybody.” Plus, because of the stability guarantees that they have “there is no big difference between Angular 4 and Angular 2.”

According to the tentative schedule, Angular 4 will be released in March 2017, Angular 5 in September/October 2017, Angular 6 in March 2018 and Angular 7 in September/October 2017 — all with minimal breaking changes.

On the road to Angular 4: Beta.5

You might also like More from author

Comments are closed, but trackbacks and pingbacks are open.