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
  • #9944
Closed
Open
Issue created Jul 14, 2021 by Administrator@rootContributor

[REQ] Elixir Package configuration

Created by: tobbbles

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

When generating an Elixir client from an OpenAPI spec, I'd like to be able to publish it to Hex, the package manager for elixir.

Currently the generated clients are unable to be published, as they are missing some required fields.

Describe the solution you'd like

I'd like for the Elixir generator to template in the needed values in mix.exs to enable publishing to Hex.

This ultimately means populating :package in project() with the following:

defp package() do
  [
    name: "{{#underscored}}{{packageName}}{{/underscored}}",
    files: ~w(lib mix.exs README* LICENSE*),
    licenses: ["{{licenseId}}"]
  ]
end

And bolstering the project definition with a :description field too.

Describe alternatives you've considered

The only alternative to render these values to is overwrite the template myself. I feel it'd be better to add this upstream.

Additional context

Assignee
Assign to
Time tracking