-
Notifications
You must be signed in to change notification settings - Fork 233
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 for AsyncAPI #539
Comments
That's a really interesting question. I think we would need to have two distinct DOM roots but we could share come of the common models. I would be reluctant to start mixing things that are unique to AsyncAPI into the same models. How would you envision adding support for it? |
Hi @darrelmiller, As there are a lot of shared building blocks, I was hoping it would be possible to build on those. I'm going to have look at it this week and next, and I'll get back to you with a little more detail in the new year. If no one else has it on the radar, it could be worth my doing that investigation Ian |
@iancooper Did you get anywhere with supporting AsyncAPI? Just had the same need on a microservice project I'm building |
@phatcher In the end we didn't end up writing anything here, we used the react templates to generate infra from the template, but have not gotten around to parsing the template from .net code. We might want to do it at some point, to validate code against the specification, but it is further off in our roadmap, for now |
I'm working on a project that needs this. If I have to write the OpenAPI definitions by hand how would I approach that? |
Hey folks, just wanted to let you know that folks from LEGO Group open sourced |
Is there any desire to extend this to cover AsyncAPI: https://www.asyncapi.com/
I am thinking of forking this to POC that, and wondered what the interest would be in extending this project to support that model too
The text was updated successfully, but these errors were encountered: