taxilang VS GoSwagger

Under the hood, the tags (and associated query language) are actually Taxi - an OSS meta-language and toolchain we build (and have shared previously).

Taxi is a relatively new entrant in the API space. It's goal is to let developers add simple, (but type-safe) tags into their APIs, so software can understand how different APIs relate to one another.

One of the gripes I have about OpenAPI is that it has a very low signal-to-noise ratio. It was bad in JSON, it's just as bad in YAML, with an added whitespace pedantry.

It's great to see a number of alternatives listed in this thread - there's much more active development in this space then I was aware of, and I hope that some of it gets upstreamed back into OpenAPI.

I'll shamelessly plug our tool in this space - Taxi (https://github.com/taxilang/taxilang), which has a dedicated DSL (not YAML) you can either use standalone, or embeddedd within OpenAPI.

I also happen to think that (for internal teams at least), generating clients on ${apiSpec} is a form of tight coupling, where producer and consumer become tied together. If you can avoid it, you should, as it allows producers and consumers to stay loosely coupled and evolve independetly without the gymnastics of avoiding breaking changes.

I've talked about this before, with proposed solutions.[0]

[0]https://orbitalhq.com/blog/2023-01-16-using-semantic-metadat...

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.