There is no disadvantage of using that approach.
The post isn’t talking about any pros/cons. It’s about parsing/converting a specific Type/Signature to a Type you need. Sometimes API can be complex to change (ex: other platforms can vary on that, or it will cause a backward compatibility issue) and send to the client a…
Hi, thank you for writing. Enforcing inheriting from BaseView won’t ensure that the reference is not null, it will ensure casting only. So yeah, a null check can be added there ☺
Kapt plugin is enabled for annotation processors.
About static entry, the post can be updated with a companion object, but because it uses `by lazy`, it generates a getter (`get()`).
Well, we can do something like:
proguardFiles getDefaultProguardFile('proguard-android.txt'), "proguard-rules-debug.pro"
proguardFiles fileTree(dir: "proguardRulesDirectory", include: ["*.pro"]).asList().toArray()
Instead of adding every Proguard file seperately, is there any disadvantage of adding all rules in a directory and include them all at once:
`proguardFiles fileTree(dir: “../allproguardrulesdirectory”, include: [“*.pro”]).asList().toArray()`?