Should flag any and all Android-related problems, not just problems in Java code e.g. checks which require consulting multiple data sources, may require multiple passes over the data, etc) Should support comprehensive and sophisticated checks (e.g. High performance : must be fast enough run all checks, all the time, without noticeably slowing down the IDE Integratable in many different types of tools, not just the IDE, and in particular, must be available as part of release build checks on continuous build servers Therefore, Android Lint is focused on Android-specific problems.ĭeeply integrated in the IDE: highlight potential errors right in the source editor These are already handled by existing code check tools, and they’re handled particularly well by IntelliJ’s code inspections, so performing the same checks in lint would just end up creating double warnings for the same errors in the source editor. Used to integrate it in Shipshape and Maven, and miscellaneous individual product builds at Google.Ĭatching general Java programming bugs. The public usage documentation for Lint is here: The potential bugs span a number of categories:Ĭorrectness (120 checks as of lint version 1.4)
Android Lint is a static analysis tool for Android which looks for 225 (261 as of May 2016) different types of Android bugs.
0 kommentar(er)
