Discussions

I am trying to publish readme docs through CLI, but I am getting this error:

I'm getting this error on my API reference page ERR-6WSW05. Can anyone help with this issue?

I currently have 3 OAS files for my 3 APIs that I need to add to our API reference in readme. Currently, syncing one file at a time will replace the other files, leaving me with only one API in my docs at a time. I am however able to manually upload multiple OAS files.

I was wondering if there was a way we can highlight new content on the Docs pages. Adding a new tag before or after the page name would be ideal.

I've tried many different styles and I put the JS Script either on the custom Javascript file or inline and they are never working.

It seems the frontend (try me) section of Readme does not properly support Int64 data type and is overflowing.

Currently working on a test project with Readme for the first time and wanted to try and bring over my Postman collection. I went through the process of creating an OpenApi file with my Postman collection but when I upload it to Readme I get an error stating:

In the API reference, under the curl request section, for some of the APIs default API schema is shown which also overrides the examples. This changes the actual API example schema.
Suggest how this can be fixed.

Let say our company have independent sso provider for authentication and oauth2 for authorization (with application code flow).. how can we integrate both?

I know that the TOC is rendered server-side, but is it possible to tweak the CSS/JS in such a way to get it to include H4s? For SEO reasons all of my guides have to start with H2s, so the H4s really act as H3s, and not having them in the TOC makes page navigation harder than I'd like.