Skip to content

Incomplete combined.oas.json generated and thus, incomplete http-client #76

@NicolasGorga

Description

@NicolasGorga

After running yarn generate:oas and yarn codegen i see that the generated spec is incomplete, as it includes no customizations (i.e no auth/seller no /vendor paths). This makes any that assumes this to have been generated to fail, for example, when a Seller tries to create a registration request, no call is made, as api.vendor. doesn't exist.

The output after running yarn generate:oas i think indicates it didn't find any customization, though inside src/api i see the oas annotations in route files and inside the openapi folder.

$ yarn generate:oas
yarn run v1.22.21
$ medusa-oas oas --type combined --paths ./src/api
🟣 Generating OAS - combined
🔵 Prefixing admin tags and operationId with Admin
🔵 Prefixing store tags and operationId with Store
🔵 Gathering custom OAS
0 files matched...
0 definitions found...
0 schemas found...
🟢 Valid OAS - combined
⚫️ Exported OAS - combined - E:\proyectos personales\mercur\apps\backend\combined.oas.json
Done in 4.94s.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions