getTypeScriptCode() can generate for Angular using $http

[nalbion]

No description provided.

[wcandillon]

@nalbion Would you like to split this PR into smaller PRs? For instance, the externalDocs option seems orthogonal. Also an example on how to use this option would be useful.

Regarding the angular typescript generation, I would make it a complete separate generator instead of being an option to be consistent with the other generators.

[nalbion]

@wcandillon would it make sense to add some extra fields to the options object?

• language - [javascript], typescript, es2015, flow, (es2015+flow?)...
• framework - node, superagent (default for typescript?), angular, polymer, reactive...

...might make it easier to create & select generators, language+'-'+framework+'-class.mustache' etc - you could even try to require(language+'-'+framework+'-generator') (and fall-back to the default impl if undefined).

[wcandillon]

@nalbion Yes maybe it is time to make things more modular now.

[nalbion]

#125 should help to ensure the output is consistent (or improved)

[nalbion]

@wcandillon - I've added language and framework fields to opts, and split my template changes into their own files

[amcdnl]

any updates on this?

[Abrissirba]

I guess this will not happen since it is over a year ago but I'm interested to know if there any other way to get the response type?