Before I build one manually is it possible to create a TypeScript definitions file from your api docs, even one to then edit and tweak manually?
It should be possible to write a script that uses our doc module to build up a TypeScript definition. Unfortunately our doc module isn't open source. You can most likely parse our docs with dox and use that output.
Keep us updated, sounds like an interesting idea. Maybe we can automate it?
Thanks @ritch I'll have a go, I would love it if you were able to automate it to keep it up to date with changes. Let me know if you guys would be willing to have a go
This is a great idea. I see the issue was closed- is a TypeScript definition file now available somewhere? Thanks
I never managed to get this sorted but would love to hear if someone does
I would love to see this. Anybody seen a TSD around for loopback?
Why was this closed? I don't see a definition file in the DefinitelyTyped repo. Can we reopen this?
This is becoming a bigger issue by the day around here; encouraged all the more by Google's own adoption of TS in Angular2, our team has pretty much committed to "TS-wherever-possible" and there's a push by some team members to re-evaluate other options (e.g., Meteor) which we had previously passed on in favor of LB for projects that are on-deck. ... not the call I'd make, but the availability of a TSD (preferably one maintained by the LB team) would certainly help those of us making the case for LB in the near term.
@ritch Was this meant to be closed? Should we reopen it?
What about generating the TSD for shared methods only? We have all the information for such signatures as part of the remoting metadata.
I've created a new issue to track the development of this feature. +1 in that thread would be nice if you want to see it done (helps us prioritize).
+1
+1. Both hapi & koa have TS definitions. Our firm is thinking of choosing these instead of loopback.
@RichardJECooke Please +1 at #1692
+1
+1
+1
+1
+1
+1
+1
+1
+1