light versions of packages

[Mkassabov]

find a way to not ship schemas maybe as tagged version called "light"

[jgoux]

On the contrary, could the "regular" package ship the openapi.json file it was generated against? I want to generate CLI commands relying on distilled SDK and having the openapi.json spec would be useful to describe the command. 👍

[Mkassabov]

@jgoux

could the "regular" package ship the openapi.json file it was generated against?

I don't see a point in that. For a few reasons:

1. not all sdks are generated using openapi. gcp uses the gcp discovery api, cloudflare uses the cloudflare ts sdk, aws uses aws-models
2. not all openapi specs are consistent. different services use different versions of openapi. some openapi implementations are yaml some are json

the way the distilled repo is laid out is everything needed to generate an sdk is in the "specs" folder which is always made up of git submodules. you can just reference the same repos distilled does. we also go out of our way to create spec repos for services that serve their specs via api, and those are publicly available as well (e.g. https://github.com/alchemy-run/distilled-spec-prisma-postgres).

Also this pr isn't reffering to the specs used to generate the sdks (we call those specs) its referring to the effect schemas being used in operations as these can be quite heavy, and validating the response of an api can both cause issues with performance and cause unnecessary validation errors if apis update in non-breaking ways (e.g. adding a field to the response) (e.g.

distilled/packages/cloudflare/src/services/pipelines.ts

Line 1696 in f47294a

export const ListSinksResponse = /*@__PURE__*/ /*#__PURE__*/ Schema.Struct({

)