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
  • #2425
Closed
Open
Issue created Mar 16, 2019 by Administrator@rootContributor

[REQ] Provide yaml support for config.json by being able to read config.yml

Created by: dragosnutu

Is your feature request related to a problem? Please describe.

It would be great to have support to pass in config.yml file instead of config.json to generate command.

Described solution

Instead of passing to generate, a config.json file using the -c parameter, we could pass in config.yml. This has multiple advantages, one of them, which is pretty important, is that we can have comments in yaml format and not in json. Using comments would be easier to know how to configure the generate.

Also maybe a great idea would be to have also a third parameter value maybe to config-help for the --format something like yamltemplate generating the default config.yml file with description as comments.

Described alternative

The alternative would be to use the old format config.json and each time we need to print the help for that/each specific language.

Assignee
Assign to
Time tracking