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
I would expect that the dropdown here would be expanded when I open the page.
Current behavior
Right now nothing happens when I change this value or anything else on the swizzled component.
Possible solution
Context
Our users don't necessarily know that that AUTHORIZATION: OAUTH can be expanded. Adding an arrow to show that this section could be expanded and closed. The section is a little cluttered for us and we wanted to remove some of the extra properties description and flows. We also wanted to add a custom variable in our spec and read it in and show it in this section as well.
Your Environment
Version used:
Docusaurus Version: 2.4.3
docusaurus-theme-openapi-docs version: 2.0.2
Environment name and version (e.g. Chrome 59, node.js 5.4, python 3.7.3): Chrome Version 124.0.6367.203
Operating System and version (desktop or mobile): MacOS 14.5 (23F79)
Describe the bug
When I swizzle (eject) ApiExplorer/SecuritySchemes, the changes I make to the index.js file do not take effect.
To keep things simple I wanted to expand the Security Schemes section by default. To accomplish this I was changing line 24 to set open to true:
{ className: "openapi-security__details", open: true }
Expected behavior
I would expect that the dropdown here would be expanded when I open the page.
Current behavior
Right now nothing happens when I change this value or anything else on the swizzled component.
Possible solution
Context
Our users don't necessarily know that that AUTHORIZATION: OAUTH can be expanded. Adding an arrow to show that this section could be expanded and closed. The section is a little cluttered for us and we wanted to remove some of the extra properties description and flows. We also wanted to add a custom variable in our spec and read it in and show it in this section as well.
Your Environment
The text was updated successfully, but these errors were encountered: