Describe the bug.

Wrong definition of payload and headers properties

Expected behavior

They must be defined as any type

{
    "headers": {
      "type":  "object",
      "description": "Example of the application headers. It can be of any type."
    },
    "payload": {
      "description": "Example of the message payload. It can be of any type."
    }
}

See:

• fix: parse message payload of any type other than map of String to Object jasyncapi#208
• [Docs Bug 🐞 report]: wrong type of payload and headers in MessageExample website#3530

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

Yes I am willing to submit a PR!