Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O openapi-generator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,476
    • Issues 3,476
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 402
    • Merge requests 402
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenAPI Tools
  • openapi-generator
  • Issues
  • #2296
Closed
Open
Issue created Mar 04, 2019 by Administrator@rootContributor4 of 5 checklist items completed4/5 checklist items

[BUG][Golang] client generations creates unreachable code

Created by: partkyle

Bug Report Checklist

  • Have you provided a full/minimal spec to reproduce the issue?
  • Have you validated the input using an OpenAPI validator (example)?
  • What's the version of OpenAPI Generator used?
  • Have you search for related issues/PRs?
  • What's the actual output vs expected output?
Description

The Go client generator creates code that cannot be reached. In the error handler all response codes are iterated over. It's not possible to have 200 level responses in this block, but they are all listed out. You can see the example here to show the issue I'm referring to. It's impossible for the status code to be >= 300 and then == 201.

openapi-generator version

4.0.0

This doesn't appear to be a regression because the problem can be seen in the sample code.

Suggest a fix

I'm not sure what's possible here, since mustache templates are logic-less. The solution may be just to leave it the way it is.

Assignee
Assign to
Time tracking