Skip to content
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

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

Open
1 of 3 tasks
CBID2 opened this issue Jan 31, 2024 · 5 comments
Open
1 of 3 tasks

Comments

@CBID2
Copy link

CBID2 commented Jan 31, 2024

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

  • I agree to follow this project's Code of Conduct
Copy link

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
Copy link
Collaborator

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.

Copy link

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

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 ❤️

@github-actions github-actions bot added the stale label Jun 13, 2024
@sambhavgupta0705
Copy link
Member

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

@github-actions github-actions bot removed the stale label Jul 26, 2024
Copy link

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

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 ❤️

@github-actions github-actions bot added the stale label Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants