-
-
Notifications
You must be signed in to change notification settings - Fork 543
swagger-to-ts considers components mandatory #262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
question
Further information is requested
Comments
This was referenced May 26, 2020
Closed
I encountered the same problem with OpenAPI schema with `paths` on top level.
What's the status of this issue and #236? Is there any work requiring external help to make schemas without |
Just merged #236, so this will go out with the next release! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running
swagger-to-ts
on a specification withoutcomponents
, it immediately fails.However,
components
is an optional part of the api schema and I can think of at least two scenarios where it would not be present:paths
schemas.yml
My specifications are quite large and I tend to split them up into separate files as per 2). This means that operations reference schemas such as
{$ref: './schemas/foo.yml#/Foo'}
.Neither of these two approaches seem to work with
swagger-to-ts
since it requirescomponents
to be present (and, I assume, also ignores any schemas outside ofcomponents
)?components
? It should be possible to fetch all externally referenced schemas using standard json-ref-parser etc?The text was updated successfully, but these errors were encountered: