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
  • #842
Closed
Open
Issue created Aug 18, 2018 by Jim Schubert@jimschubertContributor

Extract language-specific functionality from generators

Description

See #503 for a little bit of discussion on this.

Language support is currently tightly coupled to generators, often dumped into a base "abstract" type identifying the language rather than the generator.

Suggest a fix/enhancement

It would be useful if we could move language-only definitions out of generators into a LanguageOptions type or something similar. As an example, this would allow C# functionality to be shared between NancyFX, ASP.NET Core, and C# Client generators without repeating code or requiring that they all extend AbstractCSharpCodegen. Divorcing our generators from language in this way would allow us, for example, to generate these frameworks in different languages (such as F#).

Assignee
Assign to
Time tracking