Lines Matching full:lint
1 page.title=lint
17 <p>The Android {@code lint} tool is a static code analysis tool that checks your Android project source files for potential bugs and optimization improvements for correctness, security, performance, usability, accessibility, and internationalization. </p>
18 <p>For more information on running {@code lint}, see <a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a>.</p>
22 <pre>lint [flags] <project directory></pre>
25 <pre>lint myproject</pre>
27 You can also use {@code lint} to check for a specific issue. For example, you can run the following command to scan the files under the {@code myproject} directory and its subdirectories to check for XML attributes missing the Android namespace prefix. The issue ID {@code MissingPrefix} tells lint to only scan for this issue.
28 <pre>lint --check MissingPrefix myproject</pre>
30 You can create an HTML report for the issues that {@code lint} detects. For example, you can run the following command to scan the {@code myproject} directory and its subdirectories for accessibility issues, then generate an HTML report in the {@code accessibility_report.html} file.
31 <pre>lint --check Accessibility --HTML accessibility_report.html myproject</pre>
35 <p>Table 1 describes the command-line options for {@code lint}.</p>
37 <strong>Table 1.</strong> Command-line options for lint</p>
50 <td>The <code><list></code> must be a comma-separated list of {@code lint} issue IDs or categories.</td>
55 <td>Check for all the default issues supported by {@code lint} as well as the specifically enabled list of issues.</td>
56 <td>The <code><list></code> must be a comma-separated list of {@code lint} issue IDs or categories.</td>
62 <td>The <code><list></code> must be a comma-separated list of {@code lint} issue IDs or categories.</td>
85 <td>Use the specified configuration file to determine if issues are enabled or disabled for {@code lint} checking</td>
86 <td>If the project contains a {@code lint.xml} file, the {@code lint.xml} file will be used as the configuration file by default.</td>
93 <td>The report is saved in the output file specified in the argument. The HTML output includes code snippets of the source code where {@code lint} detected an issue, a verbose description of the issue found, and links to the source file.</td>
116 <td>Show the full file paths in the {@code lint} checking results.</td>
147 <td>List the command-line arguments supported by the {@code lint} tool.</td>
153 <td>List the ID and short description for issues that can be checked by {@code lint}</td>
159 <td>List the ID and verbose description for issues that can be checked by {@code lint}</td>
160 <td>Use {@code --show <ids>} to see descriptions for a specific list of {@code lint} issue IDs.</td>
165 <td>Show the {@code lint} version</td>
173 <p>To configure lint checking, you can apply the following annotation or attribute to the source files in your Android project. </p>
175 <LI>To disable lint checking for a specific Java class or method, use the <code>@SuppressLint</code> annotation. </LI>
176 <li>To disable lint checking for specific sections of your XML file, use the <code>tools:ignore</code> attribute. </li>
178 <p>You can also specify your lint checking preferences for a specific Android project in the lint.xml file. For more information on configuring lint, see <a href="{@docRoot}tools/debugging/improving-w-lint.html">Improving Your Code with lint</a>.</p>
