-
Notifications
You must be signed in to change notification settings - Fork 2
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
support loading files from uri #43
Labels
Comments
mnahkies
added
good first issue
Good for newcomers
enhancement
New feature or request
labels
Apr 22, 2023
mnahkies
added a commit
that referenced
this issue
Apr 13, 2024
initial support for loading input schemas from urls. support for following relative links to other urls probably doesn't work yet. relates #43
mnahkies
added a commit
that referenced
this issue
Apr 13, 2024
initial support for loading input schemas from urls. support for following relative links to other urls probably doesn't work yet. relates #43
mnahkies
added a commit
that referenced
this issue
Apr 13, 2024
initial support for loading input schemas from urls. support for following relative links to other urls probably doesn't work yet. relates #43
Initial support released in 0.9.0 It probably doesn't follow links to other schemas properly yet, but for standalone schemas will work fine. |
Additionally added support for authenticated remote URI's in #230 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implement support for loading definition files from URI.
Should be supported for both root/entry-point file, and also for referencing external schemas, eg:
Care needs to be taken as to relative path handling. Eg: if you reference a external file using a URL, and it references a file relatively then this should be resolved relative to the URL.
See https://datatracker.ietf.org/doc/html/draft-pbryan-zyp-json-ref-03 for exact specifications.
openapi-code-generator/packages/openapi-code-generator/src/core/file-loader.ts
Line 46 in ffc8f20
The text was updated successfully, but these errors were encountered: