You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Optional] Sponsorship to speed up the bug fix or feature request (example)
Description
I noticed, that not all metadata properties in the composer.json file are exposed to the outside.
"name": depends on the git_id/git_repo
"version": comes from the artifactVersion setting in additional-properties in the cli
"description": from the .yaml spec
"homepage", "license", "authors": are not configurable at all
Shouldn't the "name" correlate to the packageName setting inadditional-properties?
The other properties are all accessible through the info object in the yaml specification.
Bug Report Checklist
Description
I noticed, that not all metadata properties in the
composer.json
file are exposed to the outside."name"
: depends on the git_id/git_repo"version"
: comes from theartifactVersion
setting inadditional-properties
in the cli"description"
: from the.yaml
spec"homepage"
,"license"
,"authors"
: are not configurable at allShouldn't the
"name"
correlate to thepackageName
setting inadditional-properties
?The other properties are all accessible through the
info
object in theyaml
specification.openapi-generator version
openapi-generator-cli 6.3.0
OpenAPI declaration file content or url
Generation Details
openapi-generator-cli generate -i openapi/openapi.yaml -g php -o clients/php --additional-properties artifactVersion=4.1.0,packageName=my/package,invokerPackage=MyPackage\\Client --global-property skipFormModel=false
Steps to reproduce
Related issues/PRs
Suggest a fix
The text was updated successfully, but these errors were encountered: