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 Bug 🐞 report]: incorrect description of asyncapi in template documentation #1400

Open
1 task done
KunalNasa opened this issue Mar 11, 2025 · 11 comments · May be fixed by #1489
Open
1 task done

[Docs Bug 🐞 report]: incorrect description of asyncapi in template documentation #1400

KunalNasa opened this issue Mar 11, 2025 · 11 comments · May be fixed by #1489

Comments

@KunalNasa
Copy link
Contributor

KunalNasa commented Mar 11, 2025

Describe the bug you found in AsyncAPI Docs.

There is an incorrect definition of asyncapi variable on this page: page under the section of "Template generation process".

Here it is stated as "asyncapi is the original AsyncAPI document injected into your template file by default."

This is incorrect because according to the generation process steps mentioned on the introduction page of generator docs.
"The asyncapi variable is not the original AsyncAPI document but a processed version with helper functions."

Also, this contradicts the later statement that the generator passes both asyncapi and the original AsyncAPI document.

Suggested Fix on Template page:
The asyncapi (which is an instance of AsyncAPIDocument) is injected into your template file by default.

The generator passes both the asyncapi, the original AsyncAPI document, and the params to the Template Context.

Attach any resources that can help us understand the issue.

Definition of asyncapi on Generator introduction page
Image

Incorrect definition on template page under the section of "Template generation process"
Image

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Arun12-sketch
Copy link

hey @KunalNasa i want to work on this issue , could you please assigne to me.

@KunalNasa
Copy link
Contributor Author

@Arun12-sketch , issues are not assigned here. You can raise PR after the issue gets approved by maintainers.

@derberg
Copy link
Member

derberg commented Mar 26, 2025

@KunalNasa you are right, wanna open a PR or?

@KunalNasa
Copy link
Contributor Author

@derberg may I wait for @Arun12-sketch ? As he wanted to fix this issue. I will open a PR if he doesn't respond in the next 12 hours.

@Arun12-sketch
Copy link

Arun12-sketch commented Mar 26, 2025

@KunalNasa I am doing this issue .

Copy link
Member

derberg commented Mar 26, 2025

@KunalNasa are you fine with this?

@KunalNasa
Copy link
Contributor Author

@derberg yes, no problem.

Copy link
Member

derberg commented Mar 26, 2025

@Arun12-sketch go ahead with PR please

@KunalNasa
Copy link
Contributor Author

KunalNasa commented Mar 27, 2025

@Arun12-sketch I don’t think we need to go over the asynapi explanation again, especially with any changes. We’ve already covered the meaning of asyncapi in the first point, and I believe that’s sufficient for users to understand. Explaining it with additional modifications in later points could lead to confusion.

I think it would be better to discuss these doubts with the maintainers. They have a better understanding of this topic than I do, and currently I’m also a contributor like you.

@KunalNasa
Copy link
Contributor Author

Hi @Arun12-sketch, are you still working on this issue? It's been two weeks, and there are no updates on the PR. Please let me know if you need any help with the PR. I would be happy to help. Or, if you have changed your mind or have other commitments, that is totally fine. Just drop a message so that I can proceed with the PR.

Copy link
Member

derberg commented Apr 10, 2025

@KunalNasa yeah, it is one of those https://www.linkedin.com/feed/update/urn:li:activity:7295834558405431298/

Just go ahead and work on a PR

@KunalNasa KunalNasa linked a pull request Apr 11, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants