-
Notifications
You must be signed in to change notification settings - Fork 40
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
Feature request: Add a way to return topic with message #15
Comments
This isn't a perfect fix but it adds the feature for people using JSON MQTT packets The issue is to add this really you want to return {message: parsedMessage, topic} to the listener, but that would break all existing projects using this package. |
Any progress on this? |
I've implemented this feature in an up to date fork of this repository. If you would like, I can submit a merge request. |
Hey will this pull request ever be added to main branch. It passes all tests, adds a useful feature, and has been idle for over a year? |
When subscribing to wildcards a way to identify the particular topic which sent the message would be useful. If the asyncIterator returned two arguments message, topic, you could implement pubSubs that use this.
The text was updated successfully, but these errors were encountered: