[BUG] incorrect x-parser-schema-id when having multiple files

[DanielRamosAcosta]

Describe the bug.

I am encountering an issue with my asyncapi.yml file, which references schemas located in another file. When I generate the models, the generator creates generic names like AnonymousSchema_1, AnonymousSchema_2, AnonymousSchema_3, and so on for each schema in the referenced file.

After investigating the problem, I discovered that it seems to stem from the parser. Specifically, the x-parser-schema-id field in the AsyncAPIDocumentInterface object is returning values like <anonymous-schema-1>.

Expected behavior

I would expect the generated models to have the right name.

Screenshots

How to Reproduce

I will leave a PR that reproduces the error with tests.
I can try fixing the error, but I need guidance here.

Here is the reproduction: #1064

🥦 Browser

None

👀 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!

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