Skip to content

feat(openapi): migrate to openapi(swagger) 3.0 from 2.0 #253

Closed
@dzmitry-lahoda

Description

Feature Request

Migrate openapi (swagger) generator to openapi 3.0

Use Case:

I am Rust develop. All rust developers develop crypto.

And have not time to develop process-compose like thing (all attempts stalled).

Also Go people are very experienced in process orchestration things

So it is reasonable to just use Process Compose from Rust via Open API.

But Rust crates which render idiomatic rust like progenitor and okapi work only with Open API 3+, not 2.

Proposed Change:

Use Go mod to generate 3.0 OpenAPI

Who Benefits From The Change(s)?

  • All who use openapi 3.0, and cannot 2.0
  • All who wants to migrate to 3.0 as it is strictly better and safes and more precise (better generated clients).

Alternative Approaches

  • GRPC API (will fix better structured return schemas, not they are just objects)

  • yaml first approach (will fix better structured return schemas, not they are just objects)

  • convert v2 to v3 via https://github.com/getkin/kin-openapi (I am on it now, checking if it slick). UPDATE: it is not cmdcli, need to type Go code. tried https://converter.swagger.io/#/Converter/convertByContent and it converted to invalid output as (un)expected. UPDATE2: seems useless as can only produce untyped JSON in return

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions