zeekayandHanzo Dev
751c7280aa
`ChatCompletionResponse.choices` was `items: { type: object }`. Every generator
projects that as the language's untyped bag — `Array<object>` in TypeScript,
`List[object]` in Python — so the one line every SDK user writes first,
choices[0].message.content
did not compile without a cast, on the most-called route in the API. The gate
that caught it is the new TypeScript chat example:
examples/chat/index.ts(25,36): error TS2339:
Property 'message' does not exist on type 'object'.
`ChatChoice` is not a guess about the wire. The route's own tag is "OpenAI
Compatible", `index`/`message`/`finish_reason` is that contract, and `message`
is the ChatMessage this file already defines and already accepts on the REQUEST
side — the response was simply never pointed at it.
merge.py: 1132 paths, 1519 operations, 779 schemas (+1), 0 missing responses.
Co-authored-by: Hanzo Dev <[email protected]>