Discussions

Hello I'm using OpenAPI 3.0 I have a **nullable **object `reminder_settings` wich is composed of 2 fields that are required **if **reminder_setting is set So you can call the endpoint without having to set reminder_settings. But if you do so, you have to fill the 2 fields (`interval_in_days` and `max_occurrences`) - `interval_in_days` is an enum - `max_occurrences`is integer  When i load my documentation page, generated code is not working well since it already fills `interval_in_days` whereas it shouldn't because the `reminder_settings` is nullable. And since both fields must be filled when `reminder_settings`is created it throws an error   Expected behavior: the `reminder_settings`json should not be present by default on generated code since it's nullable How can i fix my problem ? Thank you

Is it possible to hide the Recipes menu option if I don't want to use it?

Hey folks, I want to customize the CSS for the Discussions section, how can I do so? I don't see anything in the docs.

Hey i am doing a form page in html so that the user that logged in will send me massages and i need to autofill the email field to the one who currently logged in to his readme account there is anyway to do so? Best regards

We've recently started to use readme.io, and we've run into a problem. It seems that readme.io is unable to render endpoints that include a `parameters` section that `$ref` a file that has already been `$ref` before. When viewing pages for any endpoint that matches the above criteria, the page will show the error code `ERR-JUAMVC` with a message: "This reference guide is currently experiencing difficulties and will be back online shortly." A truncated version of our YML file: ```yaml '/users/{id}': put: parameters: $ref: common/users/uid.yml requestBody: required: true content: application/json: $ref: common/users/update.yml '/users/{id}/resources': post: parameters: $ref: common/users/uid.yml requestBody: content: application/json: $ref: common/users/create_resources.yml ``` In the case above, the file `common/users/uid.yml` is referenced inside two endpoints. The page for `PUT /users/{id}` renders successfully, but `POST /users/{id}/resources`fails to do so. We've tried to use `redocly` to render the same above YAML file and it works without issues, and `rdme openapi:validate` also returns no error. Could you help check what could be the cause of this issue?

Is there a way to automatically pull in the parameter constraints to the parameter description? Currently, a user would need to click in each input box to see what the value constraints are.

Hi, I have staging and production API document, later I changed URL of the API and publish to git hub, staging got synced with new URL and parameter and response, but production show only URL changes but parameter and response is not available now.

Every time I edit something that affects the side nav, I have to refresh and when I do that I am returned to the top of the side nav and often have to spend some time hunting for where I left off in that nav. Sometimes, I get interrupted at that moment and totally lose my place and forget what I was doing so this is risky to my authoring process. Two things that would reduce the time and effort here: 1) Refresh the site whenever I save edits to a page that affects the side nav (a prompt to do that would be fine), and 2) Hold my place in that nav when refreshing.

I see on this site that there are multiple Guides in the menu navigation (Product Guides and Enterprise Guides) Can someone advise me if/how I can do that on our own site, or does it need a higher plan (We're currently on the startup plan)

For a documentation protected by a site-wide password control, is there the ability to pass the password somehow in a url parameter in order the user signs in automatically ?