[📑 Docs]: Missing message in "Connect to broker with MQTT client - message producer"

asyncapi / website

AsyncAPI specification website

https://www.asyncapi.com

Apache License 2.0

451 stars 603 forks source link

[📑 Docs]: Missing message in "Connect to broker with MQTT client - message producer" #2618

Open CBID2 opened 8 months ago

CBID2 commented 8 months ago

What Dev Docs changes are you proposing?

Problem

In the "Connect to broker with MQTT client - message producer" section of the Streetlights Interactive tutorial, I noticed that it does not mention the message that should be show in the first terminal. This can cause new contributors to be unsure if they have completed this activity properly.

Suggested Solution and Possible Benefit

[ ] Go to the direction that says, "Check the first terminal to see that your generated service received a message."
[ ] Replace it with the following statement: "Check the first terminal to see that your generated service received the following message: Streetlight with id "1" updated its lighting information to 3 lumens at 2017-06-07T12:34:32.000Z."

By adding this message, new contributors would see that they successfully completed the tutorial.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

github-actions[bot] commented 8 months ago

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

VaishnaviNandakumar commented 7 months ago

Hi @CBID2, the instruction to check the first terminal to check if the message was received seems to be clear enough for a user to validate if they got a response or not. The tutorial sends a single message, and the expectation is to receive the output based on it.

github-actions[bot] commented 3 months ago

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

sambhavgupta0705 commented 2 months ago

@CBID2 what's the status of this issue??