We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Same as #265
I have an OpenAPI json like that:
{ "swagger": "2.0", "definitions": { "Messages": { "type": "object", "additionalProperties": { "$ref": "#/definitions/Message" } }, "Message": { "type": "object", "properties": { "code": { "type": "integer" }, "text": { "type": "string" } } } } }
Which results in typescript:
export interface definitions { Messages: { [key: string]: ref } Message: { code?: number; text?: string } }
It is not valid, because of ref. What is ref, and why it is not defined?
openapi-typescript --version ✨ openapi-typescript 2.2
The text was updated successfully, but these errors were encountered:
Ah seems like a bug. Will investigate this week!
Sorry, something went wrong.
handle case where additionalRef is a ref (fixes openapi-ts#345)
89fc1d0
handle case where additionalRef is a ref (fixes #345) (#383)
e6673c1
* handle case where additionalRef is a ref (fixes #345) * move isOpenAPI2Reference to utils, as build-script crashes when it is in /types
Successfully merging a pull request may close this issue.
I have an OpenAPI json like that:
Which results in typescript:
It is not valid, because of ref. What is ref, and why it is not defined?
The text was updated successfully, but these errors were encountered: