Traits can be defined as double arrays

[jonaslagoni]

Describe the bug

I just noticed that the operation traits https://github.com/asyncapi/spec-json-schemas/blob/master/definitions/2.5.0/operation.json#L13 can be defined with a double array:

{
      "type": "array",
      "items": {
        "oneOf": [
          {
            "$ref": "http://asyncapi.com/definitions/2.5.0/Reference.json"
          },
          {
            "$ref": "http://asyncapi.com/definitions/2.5.0/operationTrait.json"
          },
          {
            "type": "array",
            "items": [
              {
                "oneOf": [
                  {
                    "$ref": "http://asyncapi.com/definitions/2.5.0/Reference.json"
                  },
                  {
                    "$ref": "http://asyncapi.com/definitions/2.5.0/operationTrait.json"
                  }
                ]
              },
              {
                "type": "object",
                "additionalItems": true
              }
            ]
          }
        ]
      }
    }

I don't think this is the intended behavior as it allows you to define traits such as:

asyncapi: 2.5.0
info:
  title: Account Service
  version: 1.0.0
  description: This service is in charge of processing user signups
channels:
  user/signedup:
    subscribe:
      traits: [[{summary: 'test'}]]

[derberg]

yeah, I was also confused seeing this structure when I was checking additionalItems for the other issue. I could not figure out with blame why it was added. I know @fmvilas added it but it was time when things changed sometimes without PRs.

@fmvilas do you remember why it was done like this?

[derberg]

btw it is the same with message traits -> https://github.com/asyncapi/spec-json-schemas/blob/master/definitions/2.5.0/message.json#L135

[fmvilas]

No, I honestly don't remember but it's clearly a bug.

[github-actions]

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

[asyncapi-bot]

🎉 This issue has been resolved in version 4.1.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[asyncapi-bot]

🎉 This issue has been resolved in version 5.0.0-next-major-spec.18 🎉

The release is available on:

• npm package (@next-major-spec dist-tag)
• GitHub release

Your semantic-release bot 📦🚀