spec VS GoSwagger

AsyncAPI: Interested in how to define your WebSocket APIs? One of the most advanced realtime specifications is the AsyncAPI specification, which comes with various generators for code and documentation, as well as renderers for the specifications.

Our journey with FastStream started when we needed to integrate our machine learning models into a customer's Apache Kafka environment. To streamline this process, we created FastKafka using AIOKafka, AsyncAPI, and asyncio. It was our first step in making message queue management easier.

Automatic Docs: Stay ahead with automatic AsyncAPI documentation

FastStream supports in-memory testing, AsyncAPI schema generation and more... If you are interested, please support our project by giving a GH start and joining our discord server.

However, in order for the system to work effectively, there must be a common understanding between the components regarding events and their data structures. This is where AsyncAPI comes in; it helps define a contract that describes how the components communicate and behave effectively.

You can also take a look at https://www.asyncapi.com/ (a spec for asynchronous APIs). It's useful for this use case, that is, building a well structured websocket interface with pub/sub.

Sure! Next step I am working on AsyncAPI scheme generation by your application code. It's also includes a project generation from scheme, scheme web view (lika the Swagger for OpanAPI), etc. It will a much difficult than just another broker implementation...

Onboarding - Enable developers to quickly learn how to consume the exposed APIs. For example, offer OpenAPI or AsyncAPI documentation and provide a portal and sandbox.

Hi everyone, I was going through go-swagger todo list example and came across the following implementation of server struct.

Much or some OpenAPI tooling has not even moved past OpenAPI 2.0 some even refusing and saying that they will not update to Swagger 3.0 [0] and others have issues open since some 2019 and still open with no resolution in sight (because these are individuals doing out of passion and the spec is complex to implement) and yet we have Open API spec 4.0

All this is - trying to do RPC over HTTP in a fashion that was deemed virtuous in some doctoral thesis.

I wish there were better alternatives for RPC that work everywhere including browsers.

[0]https://github.com/go-swagger/go-swagger/issues/1122#issueco...

I recommend this: https://github.com/go-swagger/go-swagger

Hi there. I am seeking any open source Schema Driven Development tool like go-swagger, but i really need to use there:

Can anyone point out what am I doint wrong? Note: I have already checked No properties generated in json file for swagger:response but didn't find anything which can help.

Try this https://github.com/go-swagger/go-swagger. It generates code for you. It is useful if only for you to generate the models/structs you could use.

go-swagger brings to the go community a complete suite of fully-featured, high-performance, API components to work with a Swagger API: - Github - Swagger 2.0 implementation for go

There is also a Code Generator that reads in a swagger file (2.0 only) and generates code for you, so all you have to do is create functions.