-
Notifications
You must be signed in to change notification settings - Fork 161
AngularJS and TypeScript #80
Comments
You mean gulp-typescript-angular ? |
I do not know, which technical build steps or dependencies have to be used. I just wanted to indicate that we should more focus on integrating TypeScript and the current AngularJS release and declare it as the standard way to go. I already heard from @hohwille, that this is currently evaluated in a project. So if it pays of, we should strongly consider to also migrate the oasp4js-sample-application to TypeScript. |
I personally can already say that it pays off. JS is still hard to write and even harder to read. When you create large applications then controllers can get quite complex. Best practices and patterns for JS help but still many pitfalls remain and single var pattern is IMHO decreasing readability. |
…ent simulaneously focusing on naming adaptions, which have been lead to confusions for users getting in touch with JS
…g aligned with server components. Tests not running.
We should strongly consider to already switch to TypeScript before the AngularJS 2.0 Release.
Due to the DefinitelyTyped descriptions, it is possible to also type the AngularJS 1.5 framework. There is a quite nice article in the 11/15 JavaMagazin covering this issue in a nice sample description. I also know from my previous company, that it is possible also for large application to already work with AngularJS and TypeScript simultaneously.
The text was updated successfully, but these errors were encountered: