-
Notifications
You must be signed in to change notification settings - Fork 77
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
Support Avro Schemas and Schema Registry #427
Comments
Welcome to Springwolf. Thanks a lot for reporting your first issue. Please check out our contributors guide and feel free to join us on discord. |
Hi @raphaeldelio Regarding the questions:
Feel free to improve the support as there are likely more people who use avro. |
Thank you for the report, the avro Schema issue has been addressed in the new release. We are working on the AsyncApi 3 release now. The current PR state passes the AsyncApi studio validation. A snapshot version for testing will be available soon. I am not aware on how to document the Kafka schema registry as part of AsyncApi. Feel free to open a new issue specific to it. |
@timonback Thank you! I will test it when the snapshot is available. |
Hi @raphaeldelio, |
@timonback just tested it and it works! I tested it with an Avro Model that has nested records as well. Thank you for this. When is this planned to be released? |
Awesome. |
Thank you very much for the shoutout on LinkedIn! Just to clarify, Avro is supported as of the current release. |
@timonback I found two bugs. One when dealing with nested avro models and another that always throws exceptions. |
Great that you provide a fix for it right away! |
Describe the feature request
When using Springwolf with Avro Models:
The example message should be:
Github Repository with project:
https://github.com/raphaeldelio/demo-springwolf
AsyncAPI Studio:
Springwolf UI:
The text was updated successfully, but these errors were encountered: