Allow build configs to be confined to specific source sets

[realh]

Would it be possible to allow a config block to be confined to a specific source set? The use case for this is that I need to test my app's ability to authenticate with a server, so I want to inject a value from the build PC's environment into the test code without it getting leaked in release builds. The existing support for targets and flavors doesn't really support this.

[RyuNen344]

@realh

Hello,

First, the code generated by BuildKonfig is output to the final artifact. It is not a Gradle Plugin intended for purposes such as hiding something.

If you want to change the values switched by BuildKonfig during testing, there is already a mechanism corresponding to the Product Flavor of the Android Gradle Plugin.
You should be able to create a flavor for testing and read the values of local environment variables during testing by setting the actual values from System.env.

https://github.com/yshrsmz/BuildKonfig?tab=readme-ov-file#product-flavor

buildkonfig {
    packageName = 'com.example.app'
    defaultConfigs {
        buildConfigField 'STRING', 'name', System.getenv("NAME") ?: "defaultName"
    }
}