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
  • #8212
Closed
Open
Issue created Dec 16, 2020 by Administrator@rootContributor5 of 6 checklist items completed5/6 checklist items

[BUG][chsarp-netcore] Underscores and spaces aren't handled properly in enum var names

Created by: sbergen

Bug Report Checklist

  • Have you provided a full/minimal spec to reproduce the issue?
  • Have you validated the input using an OpenAPI validator (example)?
  • Have you tested with the latest master to confirm the issue still exists?
  • Have you searched for related issues/PRs?
  • What's the actual output vs expected output?
  • [Optional] Sponsorship to speed up the bug fix or feature request (example)
Description

Using underscores or spaces in enum member values does not produce the correct PascalCase output, which would be expected.

openapi-generator version

Reproduces with both 4.3.1 and master

OpenAPI declaration file content or url

A model declaration along these lines will produce issues

"SomeEnum": {
  "title": "Lorem Ipsum",
  "description": "Lorem ipsum", 
  "enum": [
    "foo_bar",
    "bar baz"
  ]
}
Generation Details

Not relevant.

Steps to reproduce

Generate code for any spec with the kind of model described above. It will produce an enum with members named Foobar and Barbaz instead of the expected FooBar and BarBaz.

Related issues/PRs

I will open a PR with a fix and unit tests in a moment.

Suggest a fix

See above.

Assignee
Assign to
Time tracking