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
quarkus.openapi-generator.codegen.spec.DEFAULT_CONFIG_KEY.base-package=my.custom.package will properly generate the Api interfaces and the models in the "my.custom.package" package
quarkus.openapi-generator.codegen.spec.CUSTOM_CONFIG_KEY.base-package=my.custom.package will generate the files in the default package (which would be something like "org.openapi.quarkus.DEFAULT_CONFIG_KEY")
Is this expected behavior?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Discussed in #711
Originally posted by Nexey April 26, 2024
It seems that
quarkus.openapi-generator.codegen.spec.<filename>.base-package
doesn't support custom config keys yet.For instance:
In this scenario,
quarkus.openapi-generator.codegen.spec.DEFAULT_CONFIG_KEY.base-package=my.custom.package
will properly generate the Api interfaces and the models in the "my.custom.package" packagequarkus.openapi-generator.codegen.spec.CUSTOM_CONFIG_KEY.base-package=my.custom.package
will generate the files in the default package (which would be something like "org.openapi.quarkus.DEFAULT_CONFIG_KEY")Is this expected behavior?
Thanks in advance.
The text was updated successfully, but these errors were encountered: