Sunsetting legacy config classes

[giscus[bot]]

Sunsetting legacy config classes

Quarkus: Supersonic Subatomic Java

https://quarkus.io/blog/legacy-config-classes-sunsetting/

[hamburml]

At first I thought this means that ConfigProperty will be removed and only ConfigMapping will work. But that's not the case, right? Its only for extensions. Could you pls give an example what a legacy config class is?

[gsmet]

Yes, this is for extensions and it is about config classes that are annotated with @ConfigRoot. The new @ConfigMapping stuff has to be an interface, not a class, and annotated with both @ConfigRoot and @ConfigMapping.

See for instance a PR converting an extension from the former to the latter: https://github.com/quarkusio/quarkus/pull/46082/files .

[cescoffier]

Just to clarify: application @ConfigProperty will still work.

[radcortez]

Still, we encourage to use @ConfigMapping instead of @ConfigProperty :)

[hamburml]

To be honest I like @ConfigProperty more. It is part of mp config and I had some cases where I thought it is more flexible compared to @ConfigMapping but maybe we have used it in an impractical way. I'll get back to you on zulip with a short example when I have time :)