Hacker News Reader

Comment by josteink | Hacker News Reader

String Enums look nice. I'm also looking forward to the improved type-checking for promises and callbacks.

All in all looks like a solid release, although breaking changes means I'll be a little hesitant with updating anything critical :)

Of course, it looks like all of the breaking changes introduce compile time errors, so if you try it out and it compiles, you're good!

That's an incredibly smooth transition. Microsoft has really learned from the javaverse's mistakes regarding compatibility.

We've been using string enums for about a year now using this:

  enum StringEnums {
      aStringEnum = <any> "aStringEnum"
  }

Works great.