You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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 likeAnonymousSchema_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 theAsyncAPIDocumentInterface
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?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: