We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
I'd like for the Elixir generator to template in the needed values in mix.exs to enable publishing to Hex.
mix.exs
This ultimately means populating :package in project() with the following:
:package
project()
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.
project
:description
The only alternative to render these values to is overwrite the template myself. I feel it'd be better to add this upstream.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
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
inproject()
with the following: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
The text was updated successfully, but these errors were encountered: