taxilang
swag
taxilang | swag | |
---|---|---|
3 | 36 | |
81 | 9,839 | |
- | 2.1% | |
9.3 | 8.1 | |
2 months ago | 16 days ago | |
Kotlin | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
taxilang
-
Orbital – Dynamically unifying APIs and data with no glue code
Under the hood, the tags (and associated query language) are actually Taxi - an OSS meta-language and toolchain we build (and have shared previously).
-
Quickly modernizing SOAP APIs
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.
-
OpenAPI v4 Proposal
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...
swag
-
Seeking Advice on the Best Swagger Generation Approach for REST API
Hey Gophers, I'm exploring Swagger generation for a REST API in Go (using go-chi). Currently, I'm testing https://github.com/swaggo/swag/, but I'm uncertain if it's the optimal solution. What are your thoughts or recommendations?
- Como deixar o Swagger com tema dark mode usando Swaggo e Golang
-
Building RESTful API with Hexagonal Architecture in Go
Swaggo is a tool that creates Swagger documentation for Go APIs. It makes documenting API endpoints easier, helping developers understand and use the API.
-
go-ecommerce-microservices: A practical e-commerce microservices, built with cqrs, event sourcing, vertical slice architecture, event-driven architecture.
Some of the features: - ✅ Using Vertical Slice Architecture as a high level architecture - ✅ Using Event Driven Architecture on top of RabbitMQ Message Broker with a custom [Event Bus](pkg/messaging/bus/) - ✅ Using Event Sourcing in Audit Based services like [Orders Service](services/orders/) - ✅ Using CQRS Pattern and Mediator Patternon top of Go-MediatR library - ✅ Using Dependency Injection and Inversion of Controlon top of uber-go/fx library - ✅ Using RESTFul api with Echo framework and using swagger with swaggo/swag library - ✅ Using Postgres and EventStoreDB to write databases with fully supports transactions(ACID) - ✅ Using MongoDB and Elastic Search for read databases (NOSQL) - ✅ Using OpenTelemetry for collection Distributed Tracing with using Jaeger and Zipkin - ✅ Using OpenTelemetry for collection Metrics with using Prometheus and Grafana - ✅ Using Unit Test for testing small units with mocking dependent classes and using Mockery for mocking dependencies - ✅ Using End2End Test and Integration Test for testing features with all of their real dependeinces using docker containers (cleanup tests) and testcontainers-go library
-
OpenAPI v4 Proposal
[1]https://github.com/swaggo/swag/issues/386
-
[Request] Library Recommendation for Auto Swagger/OpenAPIv3 Documentation
I used this the other day and found it very easy to set up: https://github.com/swaggo/swag
-
Public API documentation. What to use?
I use the fizz for developing my webservices + docs, it's smooth! There is swaggo but I don`t like it because the source code get dirty (lots of comments)
-
Any Working Example for Swagger integartion with golang?
You can use swaggo/swag with code annotations
- Change host in Swagger API
-
Swagger codegen or custom tool
checkout swaggo/swag.
What are some alternatives?
openapi-codegen - A tool for generating code base on an OpenAPI schema.
GoSwagger - Swagger 2.0 implementation for go
orbital - Orbital automates integration between data sources (APIs, Databases, Queues and Functions). BFF's, API Composition and ETL pipelines that adapt as your specs change.
gin-swagger - gin middleware to automatically generate RESTful API documentation with Swagger 2.0.
smolblog - A blog engine for the social web. This is the monorepo that contains the PHP code for the project.
fiber-swagger - fiber middleware to automatically generate RESTful API documentation with Swagger 2.0.
oatx - Generator-less JSONSchema types straight from OpenAPI spec
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
speakeasy - Speakeasy CLI - Enterprise developer experience for your API
echo-swagger - echo middleware to automatically generate RESTful API documentation with Swagger 2.0.
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
jaeger - CNCF Jaeger, a Distributed Tracing Platform