asyncapi

Describe the bug
Operation bindings are described as Map[string, Operation Bindings Object] where channel bindings are described as Channel Bindings Object

I expected both definitions to be described as either Map[string, <NAME>] or <NAME>

I had opened an issue in the Shins project along these lines, but felt it might be better(?) considered here. Mermade/shins#53

To state the scenario from that issue:
Once a user is logged into our site, I'd like to be able to inject a user's API key dynamically into the API calls within the documentation. I'm using Widdershins to generate the base docs from OpenAPISp

Reason/Context

The problem is described here asyncapi/playground#79. It must be clear that returned data is not content but an object with content and metadata + what is this metadata, and that it is only with React renderer.

Description

Probably JSDoc must be only updated. Of course, some additional section in the readme would be also welcomed 😄

Reason/Context

Please try answering few of those questions

• Why we need this improvement?

Depending on the screen resolution, the menu on the right side overlay the spec content

• How will this change help?
  Allow the user to collapse this menu if needed
• What is the motivation?
  A degraded user experience

![image (13)](https://user-images.githubusercontent.com/5501911/119680927-

Describe the bug

The JavaScript generator creates constructors that requires non-required properties.

How to Reproduce

Given the following input:

{
      $id: 'TestObj',
      type: 'object',
      properties: {
        requiredProp: { type: 'string' },
        optionalProp: { type: 'string' },
      },
      required: ['requiredProp'],
}

It generates:

Reason/Context

Currently template is written in Nunjuck. We should move to JSX (aka React) renderer, of course after unification. Unfornatelly we are blocked by asyncapi/generator#521. After improving compilation of React templates, switching to React template will be very easy.

As we read in the specification about headers field for Message Object:

we validate it by the lines:

https://github.com/asyncapi/asyncapi-node/blob/master/schemas/2.1.0.json#L644-L657

However we should also validate the headers in the Message Trait Object:

https://gi

It happens 3 times in filters/all.js

• https://sonarcloud.io/project/issues?id=asyncapi_nodejs-template&issues=AXSXW9Lo1vC5408yMwFu&open=AXSXW9Lo1vC5408yMwFu
• https://sonarcloud.io/project/issues?id=asyncapi_nodejs-template&issues=AXSXW9Lo1vC5408yMwFf&open=AXSXW9Lo1vC5408yMwFf
• https://sonarcloud.io/project/issues?id=asyncapi_nodejs-template&issues=AXSXW9Lo1vC5408yMwFb&open=AXSXW9Lo1vC540