AsyncApi and OpenApi does not work together if channels are parsed

[maxdobler]

I tried this:

https://github.com/maxdobler/eventcatalog-test

I set up a eventcatalog with openapi and asyncapi generator and enabled the parseChannels: true option in the asyncapi generator.

This happened:

queries of openapi are not merged with asyncapi in the service markdown.

My guess: asyncapi generator overrides the index.mdx of the service

I expected this:

queries generated of openapi spec and events from asyncapi are both displayed in the service

Is there a workaround?

If parseChannels: false is set, the services has both queries and events

Anything else?

No response

EventCatalog Version

No response

Node.js Version

No response

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.

[maxdobler]

And it does not matter which generator runs first, if the asyncapi generator runs first the events are not in the services index.mdx.

---
id: example
version: 1.0.0
name: springwolf-example
summary: ''
schemaPath: example.openapi.json
specifications:
  openapiPath: example.openapi.json
badges: []
owners: []
setMessageOwnersToServiceOwners: true
sends: []
receives:
  - id: saveKomplex
    version: 1.0.0
---
## Architecture diagram
<NodeGraph />

[honnel]

Any update about this issue?

[boyney123]

Hey @honnel and @maxdobler thanks for raising this. We can take a look!

[honnel]

Any update on this topic?

[boyney123]

Hey @maxdobler @honnel

Thanks for raising, I spent some time diving into this, and found the problem (event-catalog/sdk#173)

When there is a id mismatch between resources in EventCatalog there becomes an issue. In this example we have a service called example and one of your channels is called example.

This is actually a Bug in the SDK (which I raised separately).

My advice to work around for now, it to ensure your service names and channel names have unique naming, until the SDK bug is fixed.

I tried it myself here and I Could get everything working as we expect when parseChannels is true.

Let me know if you still have problems!