Component
Docs
Priority
P0 - Critical (Blocking work)
SDK Language(s)
No response
Bug Description
The .md export of an API reference page omits the Errors section that the HTML page renders. Only the success response survives.
Reproducible on a Fern-hosted site that isn't ours: https://elevenlabs.io/docs/api-reference/text-to-speech/convert renders an Errors section listing 422 Unprocessable Entity Error. Append .md to that URL and the Response section contains ### 200 and nothing after it.
Same on our docs. create_chat_token declares 200, 400, 401 and 422 in the OpenAPI we supply, and https://signalwire.com/docs/apis/rest/chat-tokens/create-chat-token renders "Errors / 400 Bad Request Error / 401 Unauthorized Error / 422 Unprocessable Entity Error". The export at https://signalwire.com/docs/apis/rest/chat-tokens/create-chat-token.md ends its Response section after ### 200.
All 331 callable operations across our two OpenAPI specs declare at least one 4xx or 5xx response.
We could not find a setting for this. generators.yml has no key controlling which responses render, and our spec settings are only respect-nullable-schemas: true.
Versions
No response
Workaround
No response
Are you interested in contributing a fix?
No
Component
Docs
Priority
P0 - Critical (Blocking work)
SDK Language(s)
No response
Bug Description
The
.mdexport of an API reference page omits the Errors section that the HTML page renders. Only the success response survives.Reproducible on a Fern-hosted site that isn't ours: https://elevenlabs.io/docs/api-reference/text-to-speech/convert renders an Errors section listing
422 Unprocessable Entity Error. Append.mdto that URL and the Response section contains### 200and nothing after it.Same on our docs.
create_chat_tokendeclares 200, 400, 401 and 422 in the OpenAPI we supply, and https://signalwire.com/docs/apis/rest/chat-tokens/create-chat-token renders "Errors / 400 Bad Request Error / 401 Unauthorized Error / 422 Unprocessable Entity Error". The export at https://signalwire.com/docs/apis/rest/chat-tokens/create-chat-token.md ends its Response section after### 200.All 331 callable operations across our two OpenAPI specs declare at least one 4xx or 5xx response.
We could not find a setting for this.
generators.ymlhas no key controlling which responses render, and our spec settings are onlyrespect-nullable-schemas: true.Versions
No response
Workaround
No response
Are you interested in contributing a fix?
No