Skip to content
New issue

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

Custom config key support for base-package #753

Closed
ricardozanini opened this issue Aug 1, 2024 Discussed in #711 · 0 comments · Fixed by #800
Closed

Custom config key support for base-package #753

ricardozanini opened this issue Aug 1, 2024 Discussed in #711 · 0 comments · Fixed by #800
Assignees
Labels
area:client This item is related to the client extension bug Something isn't working

Comments

@ricardozanini
Copy link
Member

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:
image

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" 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.

@ricardozanini ricardozanini added bug Something isn't working area:client This item is related to the client extension labels Aug 1, 2024
@mcruzdev mcruzdev self-assigned this Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:client This item is related to the client extension bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants