Discussions

Is there any documentation link that explains how we can add Additional Level of Sidebar Nesting in openAPI specification in readMe. Or is there any link of example for this.

I've been trying to select a plan for my project after my free trial expired. Selecting the free plan, for instance, causes a 400 error:

I understand we can edit our profile via the readme.com dashboard but this does not change the name in when posting in discussions (currently null). Anyone know how to set our default name for all README discussions?

In writing OpenAPI files, when I want to enforce a fixed value for some key, I use an enum with a single item, as such:

I have imported a OAS file which automatically enabled Try Now button for all endpoints. I understood that I can can turn it off by setting the OpenAPI extension x-explorer-enabled to false. But, with the design our documentation page will be visible to everyone, regardless logged in or not. So I am curious how to handle the case when users not signed in yet my platform so no api key can be retrieved.

Hi there,

Currently, I can change the link color in the "Appearance" settings. But it only affects the link colors in light mode. I don't see a way to change the link color in the dark mode.

I am working to port over our docs and we use anyOf for an object type. Does readme support that structure? if not is there a workaround?

Hi, we want to share the OpenAPI specification publicly with our customers. We see that there is a public link for it("view oas"), but this link is not permanent across API versions. Could you please advise us on how to achieve what we want? The feature is much needed because some developers still prefer to import the file in Postman.

Pages are created when we specify tags in our OAS, but I wanted to add more information on this page, ideally a markdown. Is there a way for us to do this via CLI?