Recursive protobuf schema causes stackoverflow

[lukas-mertens]

Describe the bug

Recursive messages cause stackoverflow.

How to Reproduce

Define a protobuf schema with a recursion, e.g.

asyncapi: 3.0.0
info:
  title: Account Service
  version: 1.0.0
  description: This service is in charge of processing user signups
channels:
  userSignedup:
    address: user/signedup
    messages:
      UserSignedUp:
        $ref: '#/components/messages/UserSignedUp'
operations:
  sendUserSignedup:
    action: send
    channel:
      $ref: '#/channels/userSignedup'
    messages:
      - $ref: '#/channels/userSignedup/messages/UserSignedUp'
components:
  messages:
    UserSignedUp:
      payload:
        schemaFormat: application/vnd.google.protobuf;version=3
        schema: |
          syntax = "proto3";
          package Example;

          message A {
            string something = 1;
            repeated A recursive = 2;
          }

It will throw a Error thrown during AsyncAPI document parsing. Name: RangeError, message: Maximum call stack size exceeded, stack: RangeError: Maximum call stack size exceeded\n at Type.lookupTypeOrEnum

Expected behavior

Don't break. Even if it means recursive functions are not displayed properly in the generated docs, but it shouldn't make an asyncapi definition unusable, because certain things require such recursive protobuf messages

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[GreenRover]

Your example will now parsed like:

After #77 is merged

[lukas-mertens]

@GreenRover Thanks a lot!

[asyncapi-bot]

🎉 This issue has been resolved in version 3.2.5 🎉

The release is available on:

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

Your semantic-release bot 📦🚀