async api generate event documentation for both provider and client

[cjjohansen]

I tried this:

See https://github.com/cjjohansen/eventcatalog-examples/tree/main/provider-role-example

For a prepared example of the problem described in the readme.

even if we set x-eventcatalog-role:provider and client we ge multiple copies of event documentation and schema files both in provider and client service. Client should only reference documentation in provider service not duplicate it.

This happened:

I got duplicated copies of event documentation and schema files

I expected this:

I Expected a single copy under the provider/producer service

Is there a workaround?

one could accept the duplication, but it feels unnatural. What if manually add documentation what will happen?

Anything else?

See https://github.com/cjjohansen/eventcatalog-examples/tree/main/provider-role-example
"@eventcatalog/core": "^2.63.0",
"@eventcatalog/generator-asyncapi": "^5.0.4",

EventCatalog Version

@eventcatalog/core": "^2.63.0"

Node.js Version

v24.5.0

Platform(s)

No response

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.

[cjjohansen]

@boyney123
couldnt the async api generator code be changed to honor x-eventcatalog-role atribute together with channel refs ?

It seems that default async api parsing will use the message defined in the $ref spec and ignore any attempt to override the message definition