-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Composed type regression AsyncAPI 2.6.0 since v0.35.1 #185
Comments
Hallo Herr Scheidewig ! Thanks for your interest in this project, happy that it can help other developers Sorry about that, I'll correct that ! In fact, that's why I have introduced the I'll let you know when the fix is merged :) |
you don't have to apologize. i have to apologize that i didn't make a valid pr you can work with but instead mentioning that issue only. there is simply not enough time on my side to do it like that. but who am i telling that, right? ;) |
|
I'm sorry for that noise. I was too fast here. Unfortunately the issue still exists. |
thank you, mr fradin. it is fixed in v0.36.0 |
Bonjour Monsieur Fradin,
first of all thanks for that asyncapi library. It is very valuable for us 🙏
I wanted to point out, that there might be a regression in the generator since pr #168 and therefore since version
v0.35.1
of the lib.Context: we have asyncapi 2.6.0 event types based from different subtypes combined via the
allOf
attribute:the generated type for
EventPayload
contained the attributesdata
andtime
in versionv0.35.0
but in versionv.0.35.1
these are missing but the base types are still generated. i assume it should not behave like that, right?The text was updated successfully, but these errors were encountered: