BuildConfig.DEBUG is hard coded to false when we release to Maven.
If consumers use this, they won't be able to override for their tests as it in a release.
I think this does give the option that a consumer also abuses this functionality at runtime and uses it in production, but we'd need to refactor some code and extract things into another scoping-test-util module or similar.
BuildConfig.DEBUG is hard coded to false when we release to Maven.
If consumers use this, they won't be able to override for their tests as it in a release.
I think this does give the option that a consumer also abuses this functionality at runtime and uses it in production, but we'd need to refactor some code and extract things into another
scoping-test-util
module or similar.