You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using both asyncapi and openapi generators leads to unintentional behaviors
Using asyncapi generator generates the version 1 and 2 of service "Service A"
Using openapi generator for only version 2 of same service "Service A"
This happened:
The Asyncapi generator generates both service versions , Version 2 as latest and version 1 as versioned
When openapi generator executed it removes all contents of service A v1.0.0 except the specfile
I expected this:
The generator must detect the corresponding version and extend it without touching the other versions being the latest or previous ones.
Is there a workaround?
Check if the exact version exists and verify if its newer than latest or not
Add a new api method in SDk to allow adding service as a versioned one directly and if version is
The generator will create a version in versioned folder if the current service version is lower than latest
Anything else?
TWO SCREENSHOTS RPRESENTING THE PROBLEM
During OpenApi generation
After openapi spec generation ends with success
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.
The text was updated successfully, but these errors were encountered:
I tried this:
Using both asyncapi and openapi generators leads to unintentional behaviors
Using asyncapi generator generates the version 1 and 2 of service "Service A"
Using openapi generator for only version 2 of same service "Service A"
This happened:
The Asyncapi generator generates both service versions , Version 2 as latest and version 1 as versioned
When openapi generator executed it removes all contents of service A v1.0.0 except the specfile
I expected this:
The generator must detect the corresponding version and extend it without touching the other versions being the latest or previous ones.
Is there a workaround?
Check if the exact version exists and verify if its newer than latest or not
Add a new api method in SDk to allow adding service as a versioned one directly and if version is
The generator will create a version in versioned folder if the current service version is lower than latest
Anything else?
TWO SCREENSHOTS RPRESENTING THE PROBLEM
During OpenApi generation
After openapi spec generation ends with success
EventCatalog Version
No response
Node.js Version
No response
Platform(s)
No response
Community Notes
The text was updated successfully, but these errors were encountered: