-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Expand all on Response Schema #211
Comments
Hey @sixers, I've added |
Hey, any update on this? |
@sixers unfortunately no. I will try to get this done asap. If you don't see it during the next two weeks, ping me again. Thanks |
Kind of a workaround, not a very good one tho
|
Maybe also provide the similar function as the examples on the right. |
I suppose it would be better to have an option which can be passed along |
is there any update on this? I would really appreciate this feature too. |
Possible workaround. Not sure if it has negative effect: <body>
<redoc spec-url='openapi.yaml'></redoc>
<script src="https://cdn.jsdelivr.net/npm/redoc@next/bundles/redoc.standalone.js"> </script>
<script>
setTimeout(function() {
var els = document.querySelectorAll('.collapsible .collapsed');
for(el of els) {
el.classList.remove('collapsed');
}
}, 100);
</script>
</body> |
Would be great to see support for this! In the meantime, here's my workaround, using the Redoc.init(
"spec.yaml",
{
// your props here
},
document.getElementById("redoc-container"),
function () {
var els = document.querySelectorAll('td');
for (el of els) {
el.click();
}
}) |
Yes please this will pave the way for exporting to html and then to pdf with everything expanded |
Has there been any progress on this? It seems it's been "the next two weeks" since 2017 |
Thanks for checking in! No progress to report I'm afraid - but this issue will be updated when we have some news. |
I have a deeply nested response schema. Currently it's very cumbersome to see the full schema, I need to click on each nested object. ReDoc has "expand all" on example response, does it also support the same on the schema?
The text was updated successfully, but these errors were encountered: