taxilang
swagger-typescript-api
taxilang | swagger-typescript-api | |
---|---|---|
3 | 15 | |
81 | 2,951 | |
- | 3.5% | |
9.3 | 5.4 | |
2 months ago | 5 days ago | |
Kotlin | TypeScript | |
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...
swagger-typescript-api
-
Generative HTTP API Clients
RESTful APIs via swagger-typescript-api
-
Gentle Introduction To Typescript Compiler API
TypeScript API generator via Swagger scheme
- JavaScript Gom Jabbar
-
OpenAPI v4 Proposal
You said it yourself — the “official” generator is awful and very hard to modify or extend (well, you didn’t say that, but I’m saying it) and while there are many alternatives, they’re not always easy to find. I had some success with swagger-typescript-api[1], but eventually got tired of it and wrote my own generator. Despite looking around quite a bit at what’s available, I never heard of openapi-codegen, which looks quite good.
[1]: https://github.com/acacode/swagger-typescript-api
-
Fastest Way to Auto Generate Types for Typescript and ZOD Schema
A lot of APIs nowadays have a Swagger / OpenAPI spec. You can autogenerate types from that using tools like swagger-typescript-api.
-
I am so bad at connecting and debugging APIs
With such a contract your BE team should provide a https://swagger.io/tools/swagger-ui/ where the API definition can easily be viewed and tested. Also you can use generators to basically generate a boilerplate (types for all models, functions for all requests) for the entire API based on a contract: https://github.com/acacode/swagger-typescript-api This his already saved me months of work.. great tool.
-
Is putting all api calls in map actions and map getters a recommended pattern?
If your backend is using Swagger, I'd highly recommend using the package swagger-typescript-api. It auto-generates your types and endpoints for you, based on a swagger.json file, which then simplifies where I store my API calls. The flexibility of this is that I can use these API calls in components, classes, Vuex, etc., and I'm not tied to something that I have to maintain as a UI dev.
- Making an API wrapper with TypeScript
- Swagger-autogen with Typescript
-
[AskJS] What's a good option for building a backend with minimal glue code for the frontend?
If your backend is able to generate Swagger/OpenAPI JSON, you can use https://github.com/acacode/swagger-typescript-api to generate both TypeScript interfaces and an API client from the Swagger JSON.
What are some alternatives?
openapi-codegen - A tool for generating code base on an OpenAPI schema.
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
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.
swagger-ui - Swagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API.
smolblog - A blog engine for the social web. This is the monorepo that contains the PHP code for the project.
fastify-typescript-generator - generates new fastify applications in everyone's favourite language typescript with various options to choose from based on your project needs
oatx - Generator-less JSONSchema types straight from OpenAPI spec
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
speakeasy - Speakeasy CLI - Enterprise developer experience for your API
NetHack - Official NetHack Git Repository
openapi-typescript-codegen - NodeJS library that generates Typescript or Javascript clients based on the OpenAPI specification