I'm just wondering since you're using gradle now, ...

# graphql-kotlin

[Goregius]

I'm just wondering since you're using gradle now, are you going to add kapt annotation processing? Example shown here: https://spring.io/guides/tutorials/spring-boot-kotlin/#_configuration_properties

[Shane Myrick]

@Goregius Pull requests are welcome! This looks like something that we can add. I am not as familiar with all of the tools available with Gradle so if you know the best way to get config metadata please feel free to update.

We should be releasing 2.0.0 soon

[Dariusz Kuc]

configuration properties for spring server should already be available

[Dariusz Kuc]

https://github.com/ExpediaGroup/graphql-kotlin/blob/master/graphql-kotlin-spring-server/src/main/resources/META-INF/spring-configuration-metadata.json

[Dariusz Kuc]

also afaik kapt works in maven as well 😉

[Goregius]

https://github.com/ExpediaGroup/graphql-kotlin/pull/555

[Goregius]

yeah it's a minor thing, it just helps a bit since it means there's no need for the metadata file since it generates the metadata itself. And maybe it does work in maven but I think the annotation processing doesn't work which is what the spring article I linked says

[Goregius]

Currently, it outputs the metadata to build/tmp/classes/main, I'm not sure how to change this output directory currently so for right now I think the generated metadata might need to be moved manually into the resources folder.

[Dariusz Kuc]

it should be fine

[Dariusz Kuc]

if you build out a jar locally you can open up the archive and verify config metadata is under META-INF

[Goregius]

https://github.com/ExpediaGroup/graphql-kotlin/pull/556

[Goregius]

Ah yeah, it does generate the metadata, I'll remove the metadata file from sources

[Goregius]

I tested it with a local jar and imported it in another project. The properties worked, and with documentation as well.