Discussions
API Reference Results JSON Documentation
I can't find documentation on how to present different types in the JSON results
Editor widget issues
Hey,
What's the markdown for a code block that displays the language type?
What is the markdown required to emulate what you get when using the Code Sample widget? I found your documentation on how to write the markdown for a tabbed code block with a title in each tab, but I don't need two interactive tabs, just the visual look of two tabs so that the language type is displayed in tab A. In other words, exactly what you get when you use the widget.
How do you add an image using the new community discussions editor?
I cannot see a way to add an image to help explain my problem.... https://v.usetapes.com/yLjdvMHiiJ
How do I disable proxy-enabled from backend.
I need to disable proxy-enabled flag. How do I do that from the backend config?. When I was trying the "try it " feature, it was appending tryme.io in the request url. Since my API is already set to return cors headers , I need to disable it.
Is it possible to pass a list of objects to choose from to a field in readme?
It'd be nice to give my users a dropdown selector for ID instead of forcing them to copy paste from our service.
Can we link the two different contents on the same URL page?
Can we link the two different contents on the same URL page with each other?
Different alt text with the image widget?
The image widget uses the same text for the caption of a figure and for the alt text of the image. However, you might want different text, because these items have different audiences. You might use a brief description for the caption and a more detailed description for the alt text.
We only want to show the OAuth2 section in the Header and not show the apikey
We have 2 types under the SecuritySchemes node. One of them is oauth2 while the other one is apikey. Is there a way to make the apikey not visible in the API Reference page
Is there a way to expand or hide content?
In my organization's API guides, we sometimes need to list a lot (like, 30) API endpoints, which all are related to a specific functionality. Including such a list to a table or in the document body has a real negative impact on readability.