Nest: [Mqtt]The rule of topic is too strict that I can not use topic like "xx/xx/+"

Created on 4 Jan 2019  ·  7Comments  ·  Source: nestjs/nest

Current behavior

For example, I subscribe to a topic to communicate with all devices, such as "aaa/bbb/+", "+" represents the number of each device, and then handles the business logic of each device based on the business represented by "+". However, nest often adds the suffix "ack" to my topic, which leads me have no way to handle such a scene.

Expected behavior

I think nest should release the topic rules, otherwise I can't use or migrate old projects to nest

Most helpful comment

@phper-chen
We already exists, behind the scenes 😅 as Kamil said before.
We just need some how a plan, something to organize what we need to do, who will handle this task, and so on.
Kamil already doing pretty awesome, we are just asking him to organize that.

All 7 comments

The way to publish and subscribe to events without extra suffixes (both res and ack) will be provided in the next major release (6.0.0) #1350

The way to publish and subscribe to events without extra suffixes (both res and ack) will be provided in the next major release (6.0.0) #1350

Thanks, I just think you need more people to help you maintain this framework.😄

So far I cannot even work full-time on this framework. Gathering sponsors is very difficult in the OpenSource world :)

So far I cannot even work full-time on this framework. Gathering sponsors is very difficult in the OpenSource world :)

Can only expect more people with good skills to contribute to the “nestjs”.⛽️

@phper-chen
We already exists, behind the scenes 😅 as Kamil said before.
We just need some how a plan, something to organize what we need to do, who will handle this task, and so on.
Kamil already doing pretty awesome, we are just asking him to organize that.

@phper-chen You could always get involved yourself or raise bugs/feature requests so that somebody can pick them up.

You need to realise that people do this in their free time. Google is not behind this. If it doesn't meet what you need then don't use it. Nobody is forcing you.

I think your comments were not very conducive, what we don't want is for the framework to disappear - I love it.

Sometimes it takes time to get a solution, search in the forums. Its what I do.

I personally want this framework to grow - IMHO its better than anything else out their - BUT its open source.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings