Some developers may rely only on linter to detect and fix code smell. Some popular signs of code smell inside a class are a large class, too long method, complex condition, and deeply nested block. Because of its smell, these problems are easy to spot on. Code Smell DetectionĪ code smell is a surface indication that usually corresponds to a deeper problem in the system. By looking at this chart, you can refactor a dependency that has lots of methods, maybe by removing it and use an alternative dependency that has smaller method count.
Now, you can understand your codes better. You can hover your mouse to each section to learn how much methods that a package/class has. Each segment represents a package and sub-packages. To see the visualization of our app methods count, head over your project app/build/outputs/dexcount select your app_flavorDebugChart or app_flavorReleaseChart folder and open index.html file. Gradle will start building the project, and it will also print out the statistic of methods, fields and classes inside our app. That’s it, the setup phase is done! Now open a terminal and run. For the first step, add a dexcount plugin classpath in project adle classpath ':dexcount-gradle-plugin:0.8.3' In this post, we are going to use a Gradle plugin called DexCount, which not only prints out your method, field and classes count but also draws a visualization so that you can understand which dependencies are using most of your method count.īefore you start, make sure that you already have a minimum of Java 8 installed, otherwise the DexCount can’t run properly. Unfortunately, there is still no way to get rid of this, but it can be prevented by carefully adding dependencies and also by keeping an eye on your project method count.
At that point, you need to enable Dex, which may inflict more pain on you by increasing Gradle build time. In an Android project, dependencies can be added effortlessly using Gradle, and it is such a headache when you hit the method limit of 65,536. Investigate Method Count & Code Analysis in Android Kotlin Project
0 kommentar(er)
