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.

Sign up for GitHub

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

Jump to bottom

[Docs Bug 🐞 report]: wrong type of payload in MessageExample #3530

Closed
1 task done
Pakisan opened this issue Dec 31, 2024 · 3 comments · May be fixed by #3531
Closed
1 task done

[Docs Bug 🐞 report]: wrong type of payload in MessageExample #3530

Pakisan opened this issue Dec 31, 2024 · 3 comments · May be fixed by #3531
Labels
🐞 docs bug

Comments

@Pakisan
Copy link
Member

Pakisan commented Dec 31, 2024 •
edited
Loading

Describe the bug you found in AsyncAPI Docs.

According to JSON Schema MessageExample.payload may be of any type

See:

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Pakisan Pakisan changed the title [Docs Bug 🐞 report]: [Docs Bug 🐞 report]: wrong type of payload and headers in MessageExample Dec 31, 2024
Pakisan added a commit to Pakisan/website that referenced this issue Dec 31, 2024
@Pakisan
fix: wrong type of payload and headers in MessageExample
e1df5f3 
According to JSON Schema headers and payload properties may be of any type

asyncapi#3530
This was referenced Dec 31, 2024
Open
Merged
Closed
@Pakisan Pakisan changed the title [Docs Bug 🐞 report]: wrong type of payload and headers in MessageExample [Docs Bug 🐞 report]: wrong type of payload in MessageExample Jan 9, 2025
@derberg
Copy link
Member

derberg commented Jan 22, 2025

hey, why we need this issue here?

@Pakisan
Copy link
Member Author

Pakisan commented Jan 27, 2025

hey, why we need this issue here?

To bind it with PR. In a future open PR without issues?

@derberg
Copy link
Member

derberg commented Jan 27, 2025 •
edited
Loading

not in website repo

and also if it is a bug, and PR is just minute or work and minute of review - no issue needed really

@derberg derberg closed this as completed Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🐞 docs bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: wrong type of payload and headers in MessageExample Pakisan/website
2 participants
@Pakisan @derberg