Add missing TypeScript property definitions on ClientOpts #226
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aricart
approved these changes
Jun 15, 2018
|
Thanks for the contribution! |
|
No problem at all, thanks for the quick response! Are you guys happy to do a release just for this? |
|
working on it. |
|
Great, thanks a lot! |
|
nats 1.0.0 should be live! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Team,
I've been using the node.js/TypeScript client and noticed there are some missing params on connect. I checked these against the variable names used in assignOption so hopefully all is correct.
Cheers,
Chris