Skip to content
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

Adding discriminator causes spurious "recursive" notice in another schema #1735

Closed
dpkirchner opened this issue Aug 27, 2021 · 1 comment · Fixed by #2072
Closed

Adding discriminator causes spurious "recursive" notice in another schema #1735

dpkirchner opened this issue Aug 27, 2021 · 1 comment · Fixed by #2072

Comments

@dpkirchner
Copy link

Describe the bug
When adding a discriminator to one schema, the generated HTML indicates another schema is "recursive", despite no connection between the two schemas.

Expected behavior
I expected the two independent schemas to be rendered entirely.

Minimal reproducible OpenAPI snippet(if possible)

Here's the openapi.yaml and the file refs:

https://gist.github.com/dpkirchner/3e41497358e9890b70af42d704b7ec9e

Screenshots
Screen Shot 2021-08-27 at 10 19 13 AM

Additional context

User is not marked recursive if you remove the discriminator object from item.yaml.

redoc-cli: 0.12.3
redoc: 2.0.0-rc.56

Command line: redoc-cli bundle -o web/index.html ./openapi.yaml

A similar bug was closed in 2019: #695

@petersamokhin
Copy link

The same issue, with the complicated structure of files and a discriminator used somewhere ruins the whole schema models.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants