openai / openai/openai-openapi
createSpeech response content type specs.
Open
Nobody has claimed this yet.
bug
specification
- Dominant language
- No language data
- Stars
- 2.5k
- Forks
- 527
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 2
Description
createSpeech functionality specifies response.content as application/octet-stream but every request returns more specific mime type, such as audio/mpeg or audio/aac.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the createSpeech response definition in the OpenAPI specification and read how its response content types are declared. Compare the declared response type with the audio formats returned by the endpoint; done when the specification accurately represents those response MIME types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100