Update lint checks documentation snapshot

The issue documentation extraction code was improved;
it now removes more stub files, cleans up the output,
handles more corner cases in finding test examples, etc.

Author: tnorbye

docs/checks/AaptCrash.md.html

@@ -44,7 +44,6 @@
 aapt during a build. Change @+id/titlebar to @id/titlebar and define the
 id explicitly using <item type="id" name="titlebar"/> instead.
 [AaptCrash]
-
     &lt;item name="android:id"&gt;@+id/titlebar&lt;/item&gt;
     --------------------------------------------
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/checks/AcceptsUserCertificates.md.html

@@ -34,10 +34,10 @@
 :   2016
 
 Allowing user certificates could allow eavesdroppers to intercept data
-sent by your app, 'which could impact the privacy of your users.
-Consider nesting your app's `trust-anchors` inside a `<debug-overrides>`
-element to make sure they are only available when `android:debuggable`
-is set to `"true"`.
+sent by your app, which could impact the privacy of your users. Consider
+nesting your app's `trust-anchors` inside a `<debug-overrides>` element
+to make sure they are only available when `android:debuggable` is set to
+`true`.
 
 (##) Example
 
@@ -46,7 +46,6 @@
 res/xml/network_config.xml:6:Warning: The Network Security Configuration
 allows the use of user certificates in the release version of your app
 [AcceptsUserCertificates]
-
     &lt;certificates src="user"/&gt;
     --------------------------
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/checks/AccessibilityFocus.md.html

@@ -39,7 +39,6 @@
 src/com/my/app/MyView.kt:12:Warning: Do not force accessibility focus,
 as this interferes with screen readers and gives an inconsistent user
 experience, especially across apps [AccessibilityFocus]
-
     performAccessibilityAction(AccessibilityNodeInfo.ACTION_ACCESSIBILITY_FOCUS, null)
     ----------------------------------------------------------------------------------
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/checks/AccessibilityScrollActions.md.html

@@ -41,7 +41,6 @@
 and support ACTION_SCROLL_{FORWARD,BACKWARD} should also support
 ACTION_SCROLL_{LEFT,RIGHT} and/or ACTION_SCROLL_{UP,DOWN}
 [AccessibilityScrollActions]
-
   override fun onInitializeAccessibilityNodeInfo(info: AccessibilityNodeInfo) {
   ^
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/checks/AccessibilityWindowStateChangedEvent.md.html

@@ -57,29 +57,22 @@
 View.onInitializeAccessibilityNodeInfo, Activity.setTitle,
 ViewCompat.setAccessibilityPaneTitle, etc. to inform users of crucial
 changes to the UI. [AccessibilityWindowStateChangedEvent]
-
     sendAccessibilityEvent(AccessibilityEvent.TYPE_WINDOW_STATE_CHANGED)
     --------------------------------------------------------------------
-
-
 src/com/my/app/MyView.kt:16:Warning: Manually populating or sending
 TYPE_WINDOW_STATE_CHANGED events should be avoided. They may be ignored
 on certain versions of Android. Prefer setting UI metadata using
 View.onInitializeAccessibilityNodeInfo, Activity.setTitle,
 ViewCompat.setAccessibilityPaneTitle, etc. to inform users of crucial
 changes to the UI. [AccessibilityWindowStateChangedEvent]
-
     if (event.eventType == AccessibilityEvent.TYPE_WINDOW_STATE_CHANGED) {
                                               -------------------------
-
-
 src/com/my/app/MyView.kt:23:Warning: Manually populating or sending
 TYPE_WINDOW_STATE_CHANGED events should be avoided. They may be ignored
 on certain versions of Android. Prefer setting UI metadata using
 View.onInitializeAccessibilityNodeInfo, Activity.setTitle,
 ViewCompat.setAccessibilityPaneTitle, etc. to inform users of crucial
 changes to the UI. [AccessibilityWindowStateChangedEvent]
-
     if (event.eventType == AccessibilityEvent.TYPE_WINDOW_STATE_CHANGED) {
                                               -------------------------
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/checks/AccidentalOctal.md.html

@@ -40,7 +40,6 @@
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~text
 build.gradle:13:Error: The leading 0 turns this number into octal which
 is probably not what was intended (interpreted as 8) [AccidentalOctal]
-
     versionCode 010
                 ---
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/checks/ActivityIconColor.md.html

@@ -42,15 +42,11 @@
 src/test/pkg/ForegroundOnlyWalkingWorkoutService.kt:9:Warning: The
 animated icon for an ongoing activity should be white with a transparent
 background [ActivityIconColor]
-
     .setAnimatedIcon(R.drawable.animated_walk)
                      ------------------------
-
-
 src/test/pkg/ForegroundOnlyWalkingWorkoutService.kt:10:Warning: The
 static icon for an ongoing activity should be white with a transparent
 background [ActivityIconColor]
-
     .setStaticIcon(R.drawable.ic_walk)
                    ------------------
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/checks/AdapterViewChildren.md.html

@@ -40,7 +40,6 @@
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~text
 res/layout/has_children.xml:1:Warning: A list/grid should have no
 children declared in XML [AdapterViewChildren]
-
 <ListView
  --------
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/checks/AddJavascriptInterface.md.html

@@ -49,16 +49,12 @@
 WebView.addJavascriptInterface should not be called with minSdkVersion <
 17 for security reasons: JavaScript can use reflection to manipulate
 application [AddJavascriptInterface]
-
     webView.addJavascriptInterface(object, string);
             ----------------------
-
-
 src/test/pkg/AddJavascriptInterfaceTest.java:23:Warning:
 WebView.addJavascriptInterface should not be called with minSdkVersion <
 17 for security reasons: JavaScript can use reflection to manipulate
 application [AddJavascriptInterface]
-
     webView.addJavascriptInterface(object, string);
             ----------------------
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/checks/AlertDialogUsage.md.html

@@ -1,13 +1,13 @@
 <meta charset="utf-8">
-(#) Use the support library AlertDialog instead of android.app.AlertDialog.
+(#) Use the support library AlertDialog instead of android.app.AlertDialog
 
-!!! WARNING: Use the support library AlertDialog instead of android.app.AlertDialog.
+!!! WARNING: Use the support library AlertDialog instead of android.app.AlertDialog
    This is a warning.
 
 Id
 :   `AlertDialogUsage`
 Summary
-:   Use the support library AlertDialog instead of android.app.AlertDialog.
+:   Use the support library AlertDialog instead of android.app.AlertDialog
 Severity
 :   Warning
 Category
@@ -29,11 +29,45 @@
 :   Kotlin and Java files
 Editing
 :   This check runs on the fly in the IDE editor
+Implementation
+:   [Source Code](https://github.com/vanniktech/lint-rules/tree/master/lint-rules-android-lint/src/main/kotlin/com/vanniktech/lintrules/android/AlertDialogUsageDetector.kt)
+Tests
+:   [Source Code](https://github.com/vanniktech/lint-rules/tree/master/lint-rules-android-lint/src/test/kotlin/com/vanniktech/lintrules/android/AlertDialogUsageDetectorTest.kt)
 
 Support library AlertDialog is much more powerful and plays better
 together with the new theming / styling than the AlertDialog built into
 the framework.
 
+(##) Example
+
+Here is an example of lint warnings produced by this check:
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~text
+src/Test.java:4:Warning: Should not be using android.app.AlertDialog
+[AlertDialogUsage]
+  public Test(AlertDialog dialog) { }
+              ------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Here is the source file referenced above:
+
+`src/Test.java`:
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~java linenumbers
+import android.app.AlertDialog;
+
+class Test {
+  public Test(AlertDialog dialog) { }
+}
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can also visit the
+[source code](https://github.com/vanniktech/lint-rules/tree/master/lint-rules-android-lint/src/test/kotlin/com/vanniktech/lintrules/android/AlertDialogUsageDetectorTest.kt)
+for the unit tests for this check to see additional scenarios.
+
+The above example was automatically extracted from the first unit test
+found for this lint check, `AlertDialogUsageDetector.constructorParameterInJava`.
+To report a problem with this extracted sample, visit
+https://github.com/vanniktech/lint-rules/issues.
+
 (##) Including
 
 !!!