#1553 fails to generate spec on relative server urls on Windows #1565
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gracekarina
approved these changes
May 19, 2021
jhannes
added a commit
to jhannes/openapi-generator-java-annotationfree
that referenced
this pull request
May 19, 2021
jhannes
added a commit
to jhannes/openapi-generator-typescript-fetch-api
that referenced
this pull request
May 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When parsing API specs with relative server URLs when the path to the spec is specified with Windows directory separators () instead of UNIX (/), swagger-parser fails to generate OpenAPI object with no error message.
This is the cause of #1553 and most likely of OpenAPITools/openapi-generator#8266 as well