-
Notifications
You must be signed in to change notification settings - Fork 9.1k
Description
We maintain IMPLEMENTATIONS.md
which is described as
Below is a list of known tooling that implements the 3.0.0 specification
With 3.1 coming, should we start a new list of implementations as the tools start to add support?
Is the IMPLEMENTATIONS
file still useful, with other lists such as https://openapi.tools also being maintained?
There are a number of open Pull Requests to add implementations to the list, that all probably need rebasing at once. I can immediately see:
- added OpenApiClientGen #2285
- Add Cro to Server Implementations #2278 (does need a minor update)
- Add Schemathesis to IMPLEMENTATIONS.md #2206 (approved but not merged)
- Update IMPLEMENTATIONS.md #2203
- Update IMPLEMENTATIONS.md #2187
- Update IMPLEMENTATIONS.md #2182
- Update IMPLEMENTATIONS.md #1680 (changes requested)
- Added oas-tools and generator to implementations #1668
- Adding ReDoc and scc-oa3 #1662 (does need a minor update)
- Add OpenAPI Generator to IMPLEMENTATIONS.md #1600 (a tool with "openapi" in the name)
- Add networknt openapi-parser and light-codegen #1506 (includes a tool with "openapi" in the name)
(late additions)
Are there some guidelines by which we can evaluate these PRs and either merge or close them? 11 of the current 39 total PRs relate to this one file and are all minor updates that don't affect the spec itself. I'm happy to do the actual wrangling to make a single set of updates if I can get some guidance on this.