openapi-directory
orval
openapi-directory | orval | |
---|---|---|
11 | 20 | |
3,664 | 2,278 | |
1.0% | - | |
9.2 | 9.6 | |
2 days ago | 4 days ago | |
TypeScript | ||
Creative Commons Zero v1.0 Universal | 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.
openapi-directory
-
What is API Discovery, and How to Use it to Reduce Your Attack Surface
Use APIs.gurufor exploring well-documented OpenAPI files. For example, imagine you are interested in integrating a weather API. By searching for "weather" on APIs.guru, you find several options.
-
How to Automatically Consume RESTful APIs in Your Frontend
Furthermore, since we can split the generated code into multiple parts based on tag filtering, we can also create different SDKs from different resources or even publicly available APIs. There is an extensive list of publicly available OpenAPI specifications on SwaggerHub, RapidAPI and APIs.guru.
-
ApiVault: One-Stop Resource for API Integration
Maybe you'd like to integrate with APIs.guru?
https://apis.guru
- Show HN: An open-source OpenAPI package manager – openpm.ai
-
Automatic npm publishing, with GitHub Actions & npm granular tokens
In this specific case, I'm auto-publishing (now fully automatically, once a month) a package that wraps content from elsewhere bundling it with some utilities to make that useful in JS and available via NPM. For cases like this it's useful to have a patch update once a month that just updates the upstream content & republishes.
-
APIRank.dev - we crawled and ranked 5651+ public APIs from the internet 🔭
- Crawl API repositories like apis.guru
-
Making a useful REST API Specification
This should go without saying, but the types inside your API specification should be specific in order to be useful. The main way I see this appear is that some specification generators seem to default to "string" for everything, even if something else makes sense. In an analysis of 1154 specifications from OpenAPI directory, I found that 60% of the field types were strings. Many of these were instances that made sense, such as IDs or names, but many were misused types: for example, there was a year value encoded with type "string," and a boolean value with type "string" and enum "true" or "false". Using too-broad types such as strings can make it harder to understand the specification, and decrease the effectiveness of certain tools.
-
Data noob here - I’m looking to create my first ‘data’ project.. I want to create a basic data pipeline via an API with Python into SQL then to Power BI.. what are some well known live data sources that I should practice with?
I haven’t used it but have skimmed through it, but https://apis.guru has collected information on lots of APIs. You might find something interesting.
-
From OpenAPI to a working integration in minutes
Try the integration designer with your OpenAPI documents. If you don’t have any document handy, we prepared a few examples for you, or you can find more OpenAPI documents on APIs.guru.
-
What in your opinion is a growing trend? What should people and organisations be paying attention to going forward?
apis.guru is a nice site with APIs listed for many orgs.
orval
-
HonoJS: Small, simple, and ultrafast web framework for the Edges
In cases where the client needs to stay separate, we have had a good experience with Orval[1] to generate a fully-typed @tanstack/query client from our OpenAPI spec.
[1] https://orval.dev/
-
Litestar – powerful, flexible, and highly performant Python ASGI framework
- Vite/React/Tailwind for the frontend, with [Orval](https://orval.dev/) to generate FE definitions based on the API spec.
For non-API/SPA use-cases, it also has good HTML support, with built-in Jinja and HTMX integrations. The docs are great (https://docs.litestar.dev/latest/ - not quite Django-tier but that's the gold standard), however the reference application is a tad too complex imo (https://github.com/litestar-org/litestar-fullstack).
https://github.com/litestar-org/awesome-litestar has a list of useful extensions - highly recommend trying it out if you are starting a new Python web project.
-
How to Automatically Consume RESTful APIs in Your Frontend
In order to generate the API client, there are a few options available, but we are going to use (Orval)[https://orval.dev]. Orval is a CLI tool that generates API clients based on an OpenAPI specification. It supports TypeScript, JavaScript, Axios, React, Vue, Angular and Svelte and it's highly customizable.
-
Getting the most out of vscode
I would use "reveal": "never" if I don't care about the results of the command, for example, I generate swagger types using orval.dev on every folder open, but I want this to run in background as it's not that important, so I use "reveal": "never" for it.
-
Mock Service Worker(msw) releases 2.0
we started using (and now contributing to) https://orval.dev/ this year which both generates the mocks using MSW as well as the client-side networking code (React Query in our case). It removes so much boilerplate its amazing.
wrote up the basics of our workflow few weeks ago https://betaacid.co/blog/api-contracts
-
Ask HN: Why isn't JSON-RPC more widely adopted?
Personally, find gRPC-Web very attractive but the current state of TypeScript/JS code-gen is very confusing and lacking.
I would love something like https://orval.dev for gRPC-web. Have I missed something or is it just early to expect it?
I tried a few libraries but couldn't get them to work or would generate unappealing results. I believe I'm hitting this issue with my local experiments. https://github.com/grpc/grpc-web/issues/535
-
I made a framework to build fully-typed RESTful server and client with zero dependency
This is a Library I've used in the past, https://github.com/anymaniax/orval
-
Best / Modern Test Stack for a new big Next.js project
If you have OpenAPI specs to work with you could also use Orval (https://orval.dev/) to generate a lot of code. We’re just starting to evaluate it at work but so far the team that’s trialing it is liking it.
-
React & REST APIs: End-To-End TypeScript Based On OpenAPI Docs
On the frontend we can use the OpenAPI docs to generate the TS types for our data structures. Not only types but fetch functions as well as react-query hook can be generated as well. And in this blog post you can see how to do that with a library called Orval.
-
React & REST APIs: End-To-End TypeScript Based On OpenAPI Docs
On this page, we’ll use a code generator called Orval.
What are some alternatives?
postman-contract-test-generator - Postman collection and environment that will take an Open API Spec, validate component adherence, generate contract tests, and execute them.
openapi-typescript-codegen - NodeJS library that generates Typescript or Javascript clients based on the OpenAPI specification
atoz - Amazon Web Services (AWS) APIs in Nim
jest-mock-extended - Type safe mocking extensions for Jest https://www.npmjs.com/package/jest-mock-extended
SpaceX-API - :rocket: Open Source REST API for SpaceX launch, rocket, core, capsule, starlink, launchpad, and landing pad data.
react-query-auth - ⚛️ Authenticate your react applications easily with react-query.
prism - Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations.
rtk-query - Data fetching and caching addon for Redux Toolkit
awesomekql - Microsoft Sentinel, Defender for Endpoint - KQL Detection Packs
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
openapi-directory-js - Building & bundling https://github.com/APIs-guru/openapi-directory for easy use from JS
graphql-code-generator - A tool for generating code based on a GraphQL schema and GraphQL operations (query/mutation/subscription), with flexible support for custom plugins.