Skip to content

AsyncApi generator duplicate events when regenerate the catalog with different event version #136

@nunziozappulla

Description

@nunziozappulla

I tried this:

Starting with an AsyncAPI file that defines an event called myEvent and includes the following metadata: x-eventcatalog-message-version: "1"

When I update the message version to: x-eventcatalog-message-version: "2"

I notice that the service.md file shows a duplicated dispatched message:

sends:
  - id: myEvent
    version: '1'
  - id: myEvent
    version: '2'

This happened:

The old message version (which no longer exists in the AsyncAPI file) is still present in the service.md file, causing a duplication of the dispatched event.

I expected this:

I expected the AsyncAPI file to be the source of truth, meaning the service.md should only include event versions that are currently defined in the AsyncAPI file.

Is there a workaround?

No response

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions