Go to the profile of Jecelyn Yeen
Jecelyn Yeen
Coder. Diver. Speak English, Mandarin, Javascript, C# and more.

Angular 2 Final Release Finally. FINALLY.

Angular 2 reach Final Release finally. This is big. This comes just in time. Before I lose hope on Angular 2 (I almost did). The feeling of “will the day come?” kicked in after so many release candidates (RC).

I love using Angular. I’ve been actively using Angular 1 since early day and Angular 2.

If you have followed Angular 2 since early beta till RC 7. You will understand my feeling more. Let me explain my frustration a little.

What does Release Candidate (RC) mean?

A release candidate (RC) is a beta version with potential to be a final product, which is ready to release unless significant bugs emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bugs.

— Wikipedia

Let me summarize a few “surprises” that I remember.

  1. Beta 17 (Final beta before RC): ngFor use let instead of #
  2. RC 0: router suddenly become router-deprecated (if you understand my fear on “deprecated” = “legacy”)
  3. RC 2: forms become forms-deprecated (like again!?)
  4. RC 5: Introduce NgModule, a whole new way to group and import dependencies. Your bootstrap code not working.
  5. RC5 / 6: Forms changes. E.g. Form control `updateValue` to set `setValue`, Abstract control from `find` to `get`, etc.
  6. RC6: Provider syntax change. Previously, `provide(A, {useClass: …})`, now `{ provide: A, useClass: …}`
  7. RC7: Remove `ComponentMetadata` which unfortunately we are using that.
  8. Final Release: Hooray!

So, does this mean that all the above are signification bugs merge? Or Wikipedia explanation not accurate enough?

Actually, until RC4, I didn’t do any upgrade on my existing projects nor my articles on scotch.io. I don’t even write new articles.

Partially due to I’m too busy. But also to take a back seat, see what’s going to happen, and not making the team frustrated.

AND I AM FRUSTRATED AS WELL.

Because my assumption on RC should be quite stable.

Because you have tight project timeline but you need to spend times in the learn the “surprises”, making sense of it, do code changes.

Because after you take so much effort to convince the management and the team to start using Angular 2, preach about Angular 2. And the changes are so significant that you need to put in effort to update the code instead of building features. You know how much pressure I’m on.

But, Angular is Final Release now

I feel relieve. It’s so excited reading the official announcement on Angular. blog. Proprioception Reinforcement, good name.

Angular, version 2: proprioception-reinforcement
Today, at a special meetup at Google HQ, we announced the final release version of Angular 2, the full-platform…angularjs.blogspot.com.tr

The next thing I do, update all my articles on scotch.io, 10 of them at the moment.

  1. Create custom pipe in Angular 2
  2. How to Deal with Different Form Controls in Angular
  3. Using Angular 2 template-driven forms
  4. Using Angular 2 model-driven forms
  5. How to build nested model-driven forms
  6. How to implement conditional validation in model-driven forms
  7. Implement simple language translation (Part 1)
  8. Implement simple language translation (Part 2)
  9. Using HammerJS (Touch Gesture) in Angular 2
  10. How to implement custom validation directive (confirm password)

(If you don’t see any of these article updates yet, let me know, probably it’s still under review process.)

After all, most importantly, I feel the motivation to start writing on Angular 2 again. :)