-
Notifications
You must be signed in to change notification settings - Fork 66
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
ServiceBus typedef for Typescript #74
Comments
I'm not against it. How will these be used, in conjunction with servicebus? As an aside, I'd prefer the package name was changed from |
It's only used if you are including servicebus is a Typescript project. Regarding package name, that's our standard naming convention for anything I produce at work and if you did do a link-out, I'd qualify that it's third-party supported. However, I'd be more than happy to relocate and maintain it under something like mateodelnorte/servicebus-typedef which gives you full control over the naming convention :) I'm happy either way. |
Other than
What needs to be done to use the projects together? |
That's it. You can then just use an import like: import {Bus} from 'servicebus'; and Typescript can do all it's compile-time checks and balances. |
Type defs can now be installed via npm, how about a |
I'm all for whatever is easiest and most obvious to users. |
Any news regarding the @types/servicebus? |
What's the question? |
Sorry about the @types package. Another option would be to just put the d.ts file into the default package. Makes it easier to keep it in sync... |
Hi Matt. I've published a typedef for the ServiceBus here it's still pretty rough and I need to add more DocBlocks, but is this something you are interested in linking to?
The text was updated successfully, but these errors were encountered: