You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are 2 striking issues that occur when I'm trying to parse our OpenAPI specification.
When oneOf is used, the plugin parses the array into tabs, but the tab item headers are unknown. Please refer to attached screenshot which shows the specification and rendered output using Swagger Editor, compared with the plugin output
When the type is an array, nested information is not rendered. Please refer to attached screenshots as well.
To Reproduce
Load the YAML files attached at the end of the issue
Go to the page for Grant Request, which will show up nested under grant in the generated sidebar item
3. At the request body section, for the access_token field, as well as the interact field, you can see the array issue
4. Scroll further down to Responses and you can see the unknown tab title issue
Another page where this happens is the Create a quote page nested under quote in the generated sidebar item
6. Under request body, you can see the unknown tab item issue as well
7. On this page you can also see that authorizations ends up being rendered as a list item and nothing more, this might be more of a additional feature than a bug maybe?
Expected behavior
I'm not sure if the tabs are necessary, but based on the behaviour on SwaggerEditor, I suppose just putting the array index as the tab title would be better than "unknown"?
For this, the expected behaviour would be that the nested information is parsed throughly, just like it is being done for items of type object.
How often does this bug happen?
Every time
System Info
Operating System: macOS 13.5.2
Browser: Chrome
Version: 119.0.6018.4
But this issue is unrelated to the system.
Additional Context
These are the specification files where the issues occur. You can upload them to https://editor-next.swagger.io/ for see the comparison versus loading them with the plugin.
Thanks for the detailed report. These issues should be fixed in v0.3.1 that I just published on npm.
Some arrays were missing object details, they should now render correctly.
Still related to arrays, enums informations were not displayed correctly, this should now be fixed.
Regarding the "unknown" oneOf, 2 issues were involved: the labels of the tabs being "unknown" and the tabs content actually missing. Both should render correctly now.
Regarding the authorizations, each authorization is now a link to the corresponding security scheme which contains all the informations.
Describe the bug
There are 2 striking issues that occur when I'm trying to parse our OpenAPI specification.
When
oneOf
is used, the plugin parses the array into tabs, but the tab item headers are unknown. Please refer to attached screenshot which shows the specification and rendered output using Swagger Editor, compared with the plugin outputWhen the type is an array, nested information is not rendered. Please refer to attached screenshots as well.
To Reproduce
Grant Request
, which will show up nested undergrant
in the generated sidebar item3. At the request body section, for the
access_token
field, as well as theinteract
field, you can see the array issue4. Scroll further down to
Responses
and you can see the unknown tab title issueCreate a quote
page nested underquote
in the generated sidebar item6. Under request body, you can see the unknown tab item issue as well
7. On this page you can also see that authorizations ends up being rendered as a list item and nothing more, this might be more of a additional feature than a bug maybe?
Expected behavior
How often does this bug happen?
Every time
System Info
But this issue is unrelated to the system.
Additional Context
These are the specification files where the issues occur. You can upload them to https://editor-next.swagger.io/ for see the comparison versus loading them with the plugin.
The text was updated successfully, but these errors were encountered: