Typescript support

[ngbinh]

• Test for TypeScript app
• Modify build to support TypeScript
• Use tsd to automatically pull in references
• Test for TypeScript modules, controller and route
• Correct implementation of route utils
• Correct TypeScript templates
• Support other types

[dustinspecker]

Typescript is something I'd like to include in this generator (possibly Dart). Unfortunately, I don't have any experience with Typescript, so this may be a while.

[dustinspecker]

Hi,

I've been looking into TypeScript the last few days and have a few questions regarding your opinion, if you have time.

https://github.com/Keats/ng-boilerplate seems like a nice starting point. I haven't found a use for TypeScript's modules, though. Do you typically create modules when working with TypeScript? Importing the modules in a main app module doesn't sound too flexible, which are the only examples of modules used in Angular I've found.

I'm completely on board for adding TypeScript's typing, interfaces, and classes; I just want to make sure I'm not overlooking TypeScript's modules. I will probably have time to get these added soon.

[ngbinh]

Great! I am also not sure about Typescript module because it seems to share the same functionalities as angular module.

Also, I will be able to help with adding Typescript because I need it soon in a project.

[ngbinh]

I will work on this in a couple of days. Please let me know if you already started on this.

[dustinspecker]

Sounds good. I haven't started on it.

[ngbinh]

Feel free to add more tasks or take on any of them. By the look of it, I feel like utils/route is the more challenging one.

[ngbinh]

As for Typescript and AngularJs module, I feel like the current best solution is to have generate a new Typescript module along side with AngularJs module.

[dustinspecker]

I looked into this some more. TypeScript modules will need to be used, especially when passing functions is enabled. TypeScript modules allow us to have multiple functions with the same name (config, etc.) in the application, otherwise throws a compile error. Also, classes will have to be defined before we pass it to angular.module().controller(), etc. since TypeScript compiles it to JavaScript variable instead of function, so this causes hoisting issues. I'll try to get these changes added later this week/weekend, which should just about get this done. Then just the Karma issue.

[ngbinh]

Working on Karma one now

[dustinspecker]

I think I have the available typings pulled in. It also runs tsd reinstall && tsd rebundle at setup to create the typings/tsd.d.ts file. Currently, I'm using tsd@next. I've updated the app source templates and those should be working. I think there are a few typings missing. I haven't looked at the test templates, yet, but I'll have time the next couple of days to cover this and the temp directory.

[ngbinh]

Great! Thanks

[ngbinh]

FYI, I've been using TypeScript in ng-poly in production for a while without major problem. Obviously, the module system can be improved but it is not a major problem for us.

[dustinspecker]

That's great to hear. Do you guys have any suggestions for improving the modules?

The Gulpfiles have been updated to build the app and tests in a tmp directory for unit tests. The templates are updated. Unfortunately, there is an issue with angular-protractor and jQuery conflicting (DefinitelyTyped/DefinitelyTyped#2734) for e2e tests.

[ngbinh]

Awesome! Thanks a lot! I will update our build to the latest version.