Taras Mankovski

@kaos I agree - spec and implementation should be separate. We've been experimenting with this inside of our Backstage instance for integrating with our platform. We've been able to decouple...

@OrkoHunter yep, the setup that we have right now is this, 1. each service that we're consuming in Backstage has an OpenAPI spec 2. we generate clients for these services...

👋 @alexcurtin we haven't integrated with the catalog so far. We only used the clients that we created to integrate services that already have OpenAPI specs into Backstage. I might...

I'm looking at using [json-schema-to-openapi-schema](https://github.com/openapi-contrib/json-schema-to-openapi-schema) to convert at least a part of https://github.com/backstage/backstage/blob/master/packages/catalog-model/src/schema/kinds/API.v1alpha1.schema.json to YAML. From there, I'm going to try to create an OpenAPI spect that includes the routes...

> But why API? I'd have expected Entity instead, since that's the actual return type. You're right. I referenced the wrong file. It was the last file opened in my...

@freben I started creating a `@backstage/openapi` package. It'll contain the script and generated YAML files. Does that sound alright?

> We could update the ref usage but it would have to fit at least ajv and openapi at the same time. I need to customize dereferencing to support identifiers....

> Could it be useful to hand craft the api schema first, and add an integration test that builds a js client from the schema and performs calls against a...

@acunniffe 👋 I just got optic setup to start the backend and work as a proxy. It did exactly what I need it to - immediately.

@freben I want to make sure that I understand what would be beneficial at this stage. I'm going to describe some user stories that we want to be able to...