fix: make detail parameter optional in ResponseInputImage interface

[princeaden1]

• I understand that this repository is auto-generated and my pull request may not be merged

Summary

Makes the detail parameter optional in the ResponseInputImage interface to align with the documented behavior that states it "Defaults to auto".

Problem

The detail parameter was marked as required in the TypeScript interface despite the comment indicating it has a default value of 'auto'. This created unnecessary friction for developers who want to rely on the default behaviour. When the detail is omitted from the code, the openai api perform as expected but IDE will always flag detail as required (typescript). From all the examples provided on openai documentation pages, detail is optional.

Solution

Added the optional modifier (?) to the detail parameter in the ResponseInputImage interface.

Changes

• Added ? to detail parameter in ResponseInputImage interface
• Aligns TypeScript interface with documented API behaviour

Type of Change

• Bug fix (non-breaking change which fixes an issue)

Impact

This change will improve developer experience by allowing developers to omit the detail parameter when they want to use the default 'auto' behaviour.

Additional context & links

[princeaden1]

@RobertCraigie this part of the code / docs needs to be addressed, because the current example can lead to confusion when working with image URL. The OpenAI documentation example (below) doesn’t address the typing requirements for content, so when someone follows it directly, TypeScript throws errors. It took some digging to understand what was wrong and how to structure the content array correctly. Approve the two PRs (#1575) and (#1571) to save others from stress

OpenAI documentation example:

Documentation from OpenAI

Documentation from my PR #1571