-
Notifications
You must be signed in to change notification settings - Fork 129
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
Bundling leads to self-referencing component schemas #290
Comments
@glen-84 did you try the https://redoc.ly/docs/cli/commands/#bundle
It may be helpful if you can share your definition -- our email is team at redoc.ly (and please include a link to this issue). |
With
When using YAML, it completes without error, but the schemas seem to reference request and response values. This might be because of the way that our spec is structured: Paths reference separate files, the separate files reference separate files for schemas, and I'm using swagger-parser for now, but I've emailed the spec in case it's useful. Thanks. |
I had the same issue. We currently try different ways to split and structure our YAML file. In our case the problem was that we referenced a file with a list of definitions that also contains references. Snippet of main yaml
The _index.yaml contains the list to all parameters with references to the respective parameter definition. Snippet of parameters/_index.yaml
Maybe this helps. |
@tatomyr I reassigned it to me as I have some progress on it already. |
@RomanHotsiy what's the progress so far on this? and how can I help? |
Should be fixed in |
Describe the bug
When using the
bundle
command, the schemas in components.schemas reference themselves, instead of being dereferenced.Example from output:
To Reproduce
I don't have a small reproduction, as our API is large (28k lines when bundled using another tool).
I can send the spec on request, via a private channel.
Expected behavior
I expected the component schemas to be dereferenced.
Logs
n/a
OpenAPI definition
(see above)
openapi-cli
Version(s)1.0.0-beta.44
Node.js
Version(s)14.16.1
Additional context
n/a
The text was updated successfully, but these errors were encountered: