René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Invalid typedefs when spec uses same ref name for request body and schema","articleBody":"When I have a spec that defines the same thing twice (but in different namespaces) I get invalid code generated. For example, with a spec containing something like this (notice the reuse of the same identifier `myThing` for both the request body and the schema):\r\n\r\n```\r\npaths:\r\n  /my/end/point:\r\n    put:\r\n      requestBody:\r\n        $ref: '#/components/requestBodies/myThing'\r\ncomponents:\r\n  requestBodies:\r\n    myThing:\r\n      content:\r\n        application/json:\r\n          schema:\r\n            $ref: '#/components/schemas/myThing'\r\n      required: true\r\n  schema:\r\n    myThing:\r\n      type: object\r\n      properties:\r\n        thing:\r\n          type: string\r\n```\r\n\r\nThen I used up with a typedef in the generated code like: `type MyThing MyThing` which is invalid.\r\n\r\nI've currently worked around this by altering `typedef.tmpl` to do the following:\r\n\r\n```\r\n{{range .Types}}\r\n{{if ne .TypeName .Schema.TypeDecl }}\r\n{{ with .Schema.Description }}{{ . }}{{ else }}// {{.TypeName}} defines model for {{.JsonName}}.{{ end }}\r\ntype {{.TypeName}} {{if and (opts.AliasTypes) (.CanAlias)}}={{end}} {{.Schema.TypeDecl}}\r\n{{end}}\r\n{{end}}\r\n```\r\n\r\nWhich skips doing a typedef with a type name equal to it's schema declaration, but that is a bit of a hack and ideally the generator would create either unique names or be able to deduplicate identical types internally before iterating over them in the templates.","author":{"url":"https://github.com/darkliquid","@type":"Person","name":"darkliquid"},"datePublished":"2021-07-21T09:38:26Z","url":"https://github.com/oapi-codegen/oapi-codegen/issues/407"}