Shared avro model results in incorrect AsyncAPI document about generator HOT 4 CLOSED

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.

from generator.

This issue is probably a duplicate of asyncapi/avro-schema-parser#190

from generator.

I understand that for asyncapi/avro-schema-parser#190 it not at avro-schema-parser level, maybe there is anything to do at generator level ?

Would it be possible to have a kind of Model Store ? So if I have a reference to com.example.Address, it will find the model. The dependency tree has to be determined first and then the model must be treated in the correct order (from the less dependent to the most ones).

from generator.

@hguidetti there is not much we can do on generator level. Generator 100% relies on AsyncAPI object provided by https://github.com/asyncapi/parser-js. The parser is the tool where something like what you need could be provided - not sure how though. Maybe concept of custom schema parser should be extended to allow owners of parsers like avro-schema-parser to somehow prebundle schemas or something.

anyway, definitely nothing we can do in generator other than use what parser provides.

please open a separate issue in Parser with full explanation of problem. I will close this issue for now

from generator.