-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix various options definition for ts usage #1043
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
Conversation
Looing at mqtt-packet, 'will' payload should be a buffer
I've also marked 'qos' as optional on client.publish() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you mind to add some tests for the types?
Sure, I did not see we have tests on typescript definitions, I will add some. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
👍 Thanks! |
Is there any chance to get it released soon? |
* fix connect options will payload type Looing at mqtt-packet, 'will' payload should be a buffer * PR feedback * qos should be optional * add buffer/string + optional qos tests * try to stick to the file's coding style
Looking at mqtt-packet, 'will' payload should be a buffer