This repository has been archived by the owner on Nov 11, 2023. It is now read-only.
Support pulling spec from URL #169
Merged
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
qw-in
commented
Nov 6, 2019
TejasQ
requested review from
fabien0102 and
mpotomin
and removed request for
fabien0102
|
Hey @qw-in! Amazing work! We'll take a look at it in a little more detail soon and respond. |
|
Expect the little fix in |
TejasQ
approved these changes
Nov 18, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Why
We are using fastapi which generates the openapi spec so it is more convenient just to pull it right off the server
This pr adds (naive) support for grabbing specs from any http endpoint via the
-url or -uflagPS - I could not get tslint to run...kept throwing