search

asyncapi / shape-up-process

This repo contains pitches and the current cycle bets. More info about the Shape Up process: https://basecamp.com/shapeup
https://shapeup.asyncapi.io
11 stars 8 forks source link

OpenAPI, RAML, Avro, GraphQL, Protobuf, and XSD users reuse their schema/type definitions within AsyncAPI. #56

Open fmvilas opened 3 years ago

fmvilas commented 3 years ago

Description

It is common to find the same data structures defined using multiple schema/type definition languages, i.e., JSON Schema, Avro, Protobuf, GraphQL types, etc. If this outcome is achieved, users should be able to link and/or embed their definitions using any of the following languages: OpenAPI Schema, RAML Data Type, Avro, GraphQL Type, Protobuf, and XSD.

siathalysedI commented 3 years ago

We have the same issue at our work so internally we came up with a custom solution to merge all of the schema registry into a single json and attach this into a custom validator to ease the validation process and at the same time make it faster. So I created a discussion thread

https://github.com/asyncapi/community/discussions/97

Any comments are welcome

seungjinRonin commented 2 years ago

Does this issue include the goal of exporting the *.yml contract as a .proto file?

fmvilas commented 2 years ago

No, the idea of this issue is to let users reference .proto (and other) files inside an AsyncAPI document. And tools should understand it.