New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate a TypeScript Definition file as part of the build #1692
Comments
+1 |
25 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
2 similar comments
+1 |
+1 |
@ritch @ALL, microsoft is working On dts-gen, that might help to anyone working On this https://github.com/Microsoft/dts-gen |
+1 |
@M-jerez Good pointer. I'll take a look. BTW, our tooling team has built the following plugin for Visual Studio code: https://github.com/IBM-Bluemix/vscode-extension-api-connect It generates the following typescript d.ts file: |
+1 |
Stay out of this, @shairez |
Hi, i tried Qeti's fork of loopback-sdk-angular & loopback-sdk-angular-cli who generates typescript files. You can take a look here: |
Based on the work on the qeti fork, there is : |
+1 |
1 similar comment
+1 |
+1 |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
I dont know why everytime the same people rate down the post, Beeman or somebody else - feel free to tell us why you don't like that people want to keep this issue alive? |
@dasoli it's annoying to see just an If you want to express that you'd like to see this issue solved you can use the thumbs up icon on the opening post. Edit: it got mentioned here but since almost nobody tends to read they just blindly keep on adding |
@beeman no no, |
Sooo given the number of +1's (both reactions and comments) is this being prioritized at all? |
@bdharrington7 Given that the Loopback SDK Builder exists, probably not. |
@zbarbuto what if I don't want to use Angular? |
+1 |
LoopBack version 3 is in LTS, we won't be adding any new features. |
This should be possible using either the
JSDoc
comments or remoting metadata.See #1415 for original question that sparked this feature request.
The text was updated successfully, but these errors were encountered: