René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add an output option for generating a `default` case in response parsing function","articleBody":"There're times when you don't want to list all of the possible responses and you only care about a few(or you don't all of the responses), but you would like to know if there was an unexpected response. Currently using this yaml file:\n```yaml\nopenapi: 3.0.3\npaths:\n  /test:\n    post:\n      responses:\n        '200':\n          content:\n            application/json:\n              schema:\n                $ref: '#/components/schemas/Foo'\ncomponents:\n  schemas:\n    Foo:\n      type: object\n      properties:\n        bar:\n          type: string\n      required:\n        - bar\n```\nYou get such a parsing function:\n```go\nfunc ParsePostTestResponse(rsp *http.Response) (*PostTestResponse, error) {\n    bodyBytes, err := io.ReadAll(rsp.Body)\n    defer func() { _ = rsp.Body.Close() }()\n    if err != nil {\n        return nil, err\n    }\n\n    response := &PostTestResponse{\n        Body:         bodyBytes,\n        HTTPResponse: rsp,\n    }\n\n    switch {\n    case strings.Contains(rsp.Header.Get(\"Content-Type\"), \"json\") && rsp.StatusCode == 200:\n        var dest Foo\n        if err := json.Unmarshal(bodyBytes, &dest); err != nil {\n            return nil, err\n        }\n        response.JSON200 = &dest\n\n    }\n\n    return response, nil\n}\n```\nThe new output option would make the `switch` look like this:\n```go\nswitch {\n    case strings.Contains(rsp.Header.Get(\"Content-Type\"), \"json\") && rsp.StatusCode == 200:\n        var dest Foo\n        if err := json.Unmarshal(bodyBytes, &dest); err != nil {\n            return nil, err\n        }\n        response.JSON200 = &dest\n    default:\n        return nil, ErrUnexpectedResponse\n}\n```","author":{"url":"https://github.com/MilkeeyCat","@type":"Person","name":"MilkeeyCat"},"datePublished":"2025-03-12T20:02:31Z","url":"https://github.com/oapi-codegen/oapi-codegen/issues/1923"}