Boolean literals inside the BuildConfig
class are going to produce IDE warnings when using them in your code (at least within Android Studio). For example when using it in a boolean expression Android Studio will (mistakenly) recommend to simplify the boolean expression because the constant value is always the same (for current build variant that is).
This warning is only because Android Studio does not know that the final value inside BuildConfig.SOME_SETTING
may be different for other build variants.
To keep the code clean and free of warnings you can tell Android Studio to ignore this specific warning by adding an IDE comment like this:
But again this will add some noise to the code and reduce readability. By using the Boolean.parseBoolean(String)
method to initialize your constant field, you actually trick Android Studio which will no longer be able to completely analyze your boolean expressions, thus not generating warnings any longer.
This approach is very useful, as it keeps your code clean and readable, without turning off important code analysis and generation of warnings.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…