You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the things that will help to consume/expose Http-based datasets would be to be able to infer/generate OpenAPI specification for a given dataset.
Here is an example scenario, let's say we want to expose a dataset through the API (instead of granting read-only access to our filesystem/db).
One of the things that will help to consume/expose Http-based datasets would be to be able to infer/generate OpenAPI specification for a given dataset.
Here is an example scenario, let's say we want to expose a dataset through the API (instead of granting read-only access to our filesystem/db).
Let say this is our schema:
Lets build a OpenAPI specification for that endpoint:
If we take a closer look properties are 1:1 translatable to/from Flow Schema.
We can add it as a new Bridge
src/bridge/openapi/flow/
that would provide two converters:The text was updated successfully, but these errors were encountered: