https://github.com/rrjanbiah/legacy2openapi-spec

Legacy to OpenAPI spec conversions of APIs for easy SDK code generations
https://github.com/rrjanbiah/legacy2openapi-spec

openapi openapi-generator openapi-spec openapi-specification openapi3 swagger swagger-api

Last synced: about 1 month ago
JSON representation

Legacy to OpenAPI spec conversions of APIs for easy SDK code generations

• Host: GitHub
• URL: https://github.com/rrjanbiah/legacy2openapi-spec
• Owner: rrjanbiah
• License: mit
• Created: 2022-04-23T14:47:43.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2022-04-23T15:25:53.000Z (over 2 years ago)
• Last Synced: 2024-10-01T06:44:07.652Z (about 2 months ago)
• Topics: openapi, openapi-generator, openapi-spec, openapi-specification, openapi3, swagger, swagger-api
• Language: Rust
• Homepage:
• Size: 3.91 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# legacy2openapi-spec - Legacy to OpenAPI spec conversions of APIs for easy SDK code generations

OpenAPI spec-compliant APIs have the below advantages:

1. Can generate SDK codes automatically using the [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator)

2. Can generate API playground & documentation using [openapi-ui](https://github.com/dhcode/openapi-ui) and [Swagger UI](https://github.com/swagger-api/swagger-ui)

3. Can generate nice-looking documentation using [Redoc](https://github.com/Redocly/redoc)

But, few SaaS companies don't offer OpenAPI spec for their own reasons. This project is an attempt to identify those legacy API documentation and convert them into OpenAPI spec.