Discussions

Hello I face an issue when using multipart/form-data and object in body. Here is snapshot of current openapi 3.0  The problem is with `initials` and its content: `alignment` and` y` In documentation generated code looks like this:  In shell generated, we can see `--form alignment=hello --form y=10` Whereas i would expect `--form initials[alignment]=hello --form initials[y]=10` When using `application/json` instead of `multipart/form-data `is works very well, so i'm assuming this is a generation code problem related to `multipart/form-data`. Within the same endpoint i'm also upload a file so i need to keep `multipart/form-data` You can see our public doc here: <https://developers.yousign.com/reference/post-signature_requests-signaturerequestid-documents> Could you help me one this one, or tell me when this will be fixed ? Thanks

The doc says there is slack integration for Suggested Edits and Discussions. Is there any support for changelogs? <https://docs.readme.com/main/docs/slack>

The youtube embed doesn't accept the share/embed privacy mode which domain is: ``` www.youtube-nocookie.com ``` Would be helpful for those who care about privacy.

It seems readme is only available in a cloud-based server model. Or do you also provide an in-house server model?

Can I provide redirects to third-party websites in ReadMe pages?

I'm trying to hide the TOC in my ReadMe project, but the TOC remains visible despite making changes. Any suggestions on how to successfully hide the TOC?

Like i need to pass payload like this way for questions and nestedquestions need to pass empty array. { "attri": [ { "key": "First Name", "value": "Kk" }, { "key": "Last Name", "value": "Ppp" }, { "key": "Email", "value": "[email protected]" } ], "questions": \[], "nestedQuestions": \[], "seatNumber": null, "eventTicketingId": null, "eventKey": null }

Could we have like a wizard procedure now?

Can you place a Hubspot or Zoominfo tracking pixel on a Readme.com doc?

I am facing this issue "unknown error(cannot read the properties of null ('reading slug'))" while deploying OAS through github. could someone help me to resolve this issue. As a developer, I am working on documentation for API changes. Due to support of multiple base URL's, I upgraded to OAS 3.0 from OAS 2.0. After that I started facing this issue. If i update readme keys (API_DEFINITION_KEY & Readme key), then the build is successfull. But after deploying few more changes suddenly this issue replicating. I did validating my OAS file using swagger editor and no error in it. could you pleae reproduce this isssue on your side and provide me the solution.