Skip to content

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

Merged
merged 5 commits into from
Feb 11, 2020
Merged

Conversation

vincent-tr
Copy link
Contributor

Looking at mqtt-packet, 'will' payload should be a buffer

Looing at mqtt-packet, 'will' payload should be a buffer
@vincent-tr
Copy link
Contributor Author

I've also marked 'qos' as optional on client.publish()

@vincent-tr vincent-tr changed the title fix connect options will payload type fix various options definition for ts usage Feb 10, 2020
@vincent-tr vincent-tr requested a review from mcollina February 10, 2020 16:54
Copy link
Member

@mcollina mcollina left a 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?

@vincent-tr
Copy link
Contributor Author

Sure, I did not see we have tests on typescript definitions, I will add some.

@vincent-tr vincent-tr requested a review from mcollina February 11, 2020 14:41
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@mcollina mcollina merged commit b77241c into mqttjs:master Feb 11, 2020
@vincent-tr
Copy link
Contributor Author

👍 Thanks!

@vincent-tr vincent-tr deleted the patch-1 branch February 11, 2020 16:18
@vincent-tr
Copy link
Contributor Author

vincent-tr commented Feb 11, 2020

Is there any chance to get it released soon?

PremiumBurger pushed a commit to quickstar/MQTT.js that referenced this pull request Nov 27, 2020
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants