AsyncApi generator duplicate events when regenerate the catalog with different event version
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 44/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- api
Research direction
Start by locating the AsyncAPI generator entry point and the regeneration logic that writes service.md, then reproduce the issue by changing x-eventcatalog-message-version from 1 to 2. Done means regeneration removes the obsolete version and service.md lists only the currently defined event version; add or update a regression test if the generator has coverage for this output.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- TypeScript
- Stars
- 15
- Forks
- 15
- Avg merge
- 3m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from event-catalog/generators
-
Difficulty 4/5 3-5 days Newbie friendliness 56/100
event-catalog/generators#458 ·
-
generator-asyncapi: option to default message (and channel) versions to the document's info.versionOpen
Difficulty 4/5 3-5 days Newbie friendliness 55/100
event-catalog/generators#457 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
event-catalog/generators#451 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
event-catalog/generators#450 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
event-catalog/generators#449 · 1 comment ·
All issues in event-catalog/generators
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Graphify-Labs/graphify#4860 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sveltejs/eslint-plugin-svelte#1615 ·
Maintainers usually reply within 7 days
-
Parallel reticle_verify opens per-flow leases without the source lease's ignoreHTTPSErrorsPossibly taken @as992949791 claimed this today. Opengood first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
reticlehq/reticle#2033 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day