René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Name conflict of components/schemas and operationId response objects","articleBody":"I attempted to generate a client using the official OpenAI specifications found at [GitHub - openai/openai-openapi](https://github.com/openai/openai-openapi/blob/a7a0b63d1fac3acac9a223d57da1219c8a97c01e/openapi.yaml), but encountered a naming conflict.\r\n\r\nFor example:\r\n```yaml\r\nopenapi: 3.0.0\r\ninfo:\r\n  title: OpenAI API\r\n  version: 2.0.0\r\npaths:\r\n  /assistants:\r\n    get:\r\n      operationId: listAssistants\r\n      responses:\r\n        \"200\":\r\n          description: OK\r\n          content:\r\n            application/json:\r\n              schema:\r\n                $ref: \"#/components/schemas/ListAssistantsResponse\"\r\ncomponents:\r\n  schemas:\r\n    ListAssistantsResponse:\r\n      type: string\r\n```\r\n\r\nThis specification generates two types:\r\n```go\r\n// this for schemas\r\ntype ListAssistantsResponse = string\r\n\r\n// and this for response object\r\ntype ListAssistantsResponse struct {\r\n\tBody         []byte\r\n\tHTTPResponse *http.Response\r\n\tJSON200      *ListAssistantsResponse\r\n}\r\n```\r\nI'm considering making a merge request to fix this, but I'm unsure of the best approach. Here are some options:\r\n\r\n1. Rename the response object to operationID+OperationResponse or something similar.\r\n2. Append a suffix like Model to all schemas.\r\n3. Identify all conflicts at the end of generation and rename one of them.\r\n","author":{"url":"https://github.com/Hrom-in-space","@type":"Person","name":"Hrom-in-space"},"datePublished":"2023-11-17T14:05:01Z","url":"https://github.com/oapi-codegen/oapi-codegen/issues/1357"}