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

open-api-normalizer configuration key unrecognized #644

Open
enrico-niccoli opened this issue Jan 29, 2024 · 2 comments
Open

open-api-normalizer configuration key unrecognized #644

enrico-niccoli opened this issue Jan 29, 2024 · 2 comments
Labels
area:client This item is related to the client extension good first issue Good for newcomers help wanted Extra attention is needed pinned Issues and PRs that must not stale

Comments

@enrico-niccoli
Copy link

Hi everyone,

I'm using quarkus-openapi-generator to generate code from a contract with 10 Tags, one for each endpoint. This produces 10 different Api interface files but I would need to compress everything in a single interface.

Searching on the web I found the normalizer config SET_TAGS_FOR_ALL_OPERATIONS=MySingleTag to generate a single file, so I added the property
quarkus.openapi-generator.codegen.spec.my_custom_name.open-api-normalizer=SET_TAGS_FOR_ALL_OPERATIONS=MySingleTag since open-api-normalizer is listed as a supported configuration

But, at compile time, I receive this warning and openapi-generator still produces 10 different classes:
[WARNING] [io.quarkus.config] Unrecognized configuration key "quarkus.openapi-generator.codegen.spec.my_custom_name.open-api-normalizer" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo

Am I missing something? Is there some extra dependency to add?

Thanks,
Enrico

@ricardozanini
Copy link
Member

Hi Enrico!

Thanks for this issue. Currently, we are not implementing this feature. This extension is not a carbon copy of the original Maven plugin. We have to implement those features as requested since we have to match the Quarkus environment.

It shouldn't be hard to implement, if you want you can send a PR since I believe the maintainers don't have bandwidth atm.

@ricardozanini ricardozanini added area:client This item is related to the client extension good first issue Good for newcomers help wanted Extra attention is needed labels Feb 27, 2024
Copy link
Contributor

@ricardozanini @hbelmiro This is being labeled as Stale.

@github-actions github-actions bot added the Stale label Apr 28, 2024
@hbelmiro hbelmiro added pinned Issues and PRs that must not stale and removed Stale labels Apr 28, 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 good first issue Good for newcomers help wanted Extra attention is needed pinned Issues and PRs that must not stale
Projects
None yet
Development

No branches or pull requests

3 participants