openai / openai/openai-openapi
Consider renaming the models that extend `ItemResource` for consistency
Open
Nobody has claimed this yet.
enhancement
specification
- Dominant language
- No language data
- Stars
- 2.5k
- Forks
- 527
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 2
Description
Currently, some of the models that extend ItemResource include the "*Resource" suffix in their name:
- InputMessageResource
- ComputerToolCallOutputResource
- FunctionToolCallResource
- FunctionToolCallOutputResource
- MCPApprovalResponseResource
But others don't:
- OutputMessage
- FileSearchToolCall
- ComputerToolCall
- WebSearchToolCall
- ImageGenToolCall
- CodeInterpreterToolCall
- LocalShellToolCall
- LocalShellToolCallOutput
- MCPListTools
- MCPApprovalRequest
- MCPToolCall
This inconsistency makes the spec harder to read. Consider adding the "*Resource" suffix to all models that extend ItemResource.
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
No file or test is named in the issue. Start by locating ItemResource and the listed models in the OpenAPI specification, then check how model references and generated artifacts are handled. Done means all models extending ItemResource use the Resource suffix consistently and the specification remains valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100