Circular references in referenced OpenAPI broken: Error: Token "ChildObject" does not exist.

[daniel-sc]

Describe the bug

I get the following error on running ag asyncapi.yaml @asyncapi/html-template:

Something went wrong:
Error: Token "ChildObject" does not exist.
    at dereference (c:\devsbb\eaio-ng\nodejs\16\node_modules\@asyncapi\generator\node_modules\@asyncapi\parser\lib\parser.js:160:11)
    at handleCircularRefs (c:\devsbb\eaio-ng\nodejs\16\node_modules\@asyncapi\generator\node_modules\@asyncapi\parser\lib\parser.js:174:3)
    at parse (c:\devsbb\eaio-ng\nodejs\16\node_modules\@asyncapi\generator\node_modules\@asyncapi\parser\lib\parser.js:109:35)
    at Generator.generateFromString (c:\devsbb\eaio-ng\nodejs\16\node_modules\@asyncapi\generator\lib\generator.js:265:22)
    at c:\devsbb\eaio-ng\nodejs\16\node_modules\@asyncapi\generator\cli.js:154:9

Observation 1: When the circular refrence in ChildObject is removed, the generation works fine!
Observation 2: When both schemas (ChildObject, ParentObject) are defined inside asyncapi.yaml everything works fine as well!

How to Reproduce

asyncapi.yaml:

asyncapi: 2.0.0
info:
  title: Account Service
  version: 1.0.0
  description: "This service is in charge of processing user signups :rocket:"
channels:
  user/parent:
    subscribe:
      message:
        payload:
          $ref: 'openapi.yaml#/components/schemas/ParentObject'
  user/child:
    subscribe:
      message:
        payload:
          $ref: 'openapi.yaml#/components/schemas/ChildObject'
components:
  schemas: {}

openapi.yaml:

openapi: 3.0.3
info:
  title: Title
  description: Title
  version: 1.0.0
servers:
  - url: 'https'
paths: { }
components:
  schemas:
    ParentObject:
      type: object
      properties:
        child:
          $ref: '#/components/schemas/ChildObject'
    ChildObject:
      type: object
      properties:
        sister:
          $ref: '#/components/schemas/ChildObject'

Expected behavior

Expect to generate successfully.

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

[daniel-sc]

This is still an open 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 ❤️

[daniel-sc]

This is still open and relevant

[jonaslagoni]

I actually think this is a bug in a library the parser is using, this sounds related to the following: APIDevTools/json-schema-ref-parser#308

[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.

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

[daniel-sc]

Not stale

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