Update lint docs to current versions

Author: tnorbye

docs/api-guide.html

@@ -432,6 +432,7 @@
 This is a \`code symbol\`    | This is a `code symbol`
 This is `*italics*`          | This is *italics*
 This is `**bold**`           | This is **bold**
+This is `~~strikethrough~~`  | This is ~~strikethrough~~
 http://, https://            | [](http://), [](https://)
 `\*not italics*`             | `\*not italics*`
 \`\`\`language\n text\n\`\`\`| (preformatted text block)
@@ -787,7 +788,7 @@
         val incident = Incident(context, ISSUE)
             .message( "Use `<vector>` instead of `<bitmap>`")
             .at(element)
-        context.report(incident))
+        context.report(incident)
     }
 }
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -894,7 +895,7 @@
 Line 1 says we want to have line 3 called whenever lint comes across a
 method to `setRepeating`.
 
-On lines 8-4 we make sure we're talking about the correct method on the
+On lines 8-14 we make sure we're talking about the correct method on the
 correct class with the correct signature. This uses the `JavaEvaluator`
 to check that the called method is a member of the named class. This is
 necessary because the callback would also be invoked if lint came
@@ -1067,7 +1068,7 @@
 wrappers yourself, via `UBinaryExpression.asCall()`,
 `UUnaryExpression.asCall()`, and `UArrayAccessExpression.asCall()`.
 
-There is also a visitor you can use to visit call calls --
+There is also a visitor you can use to visit all calls --
 `UastCallVisitor`, which will visit all calls, including those from
 array accesses and unary operators and binary operators.
 

docs/api-guide/basics.md.html

@@ -5,6 +5,49 @@
 information about user visible changes to lint, see the User
 Guide.
 
+**8.4**
+
+* You can now use `~~` in text messages (error messages, issue
+  explanations, etc) to create strikethrough text. For example, “`Don't
+  do this: ~~super.onCreate()~~`” will render as “Don't do this:
+  ~~super.onCreate()~~”.
+
+**8.3**
+
+* If you'd like to change your error message reported by your
+  detector, you can now override your `Detector`'s `sameMessage`
+  method: match the details in the previous error message with the
+  new format. This is used by the baseline mechanism such that your
+  message change doesn't suddenly invalidate all existing baseline
+  files for your issue.
+
+* The replace-string quickfix descriptor now lets you replace a string
+  repeatedly. Example:
+  ```
+  fix().replace().text("Foo").with("Bar").repeatedly().build()
+  ```
+
+  You can also match an element optionally. Example:
+  ```
+  fix().composite(
+    fix().replace().text("<Tag>").with("<tag>").build(),
+     fix().replace().text("</Tag>").with("</tag>").optional().build()
+  )
+  ```
+
+* The quickfix machinery was improved significantly. It now does a
+  better job inserting imports (in alphabetical order instead of always
+  prepending to the import list), inserting new XML attributes in the
+  right canonical Android order, cleaning up whitespace after edits,
+  etc. This may result in some diffs in any quickfix-related unit tests
+  (e.g. `lint().run().expectFixDiffs(...)`)
+
+* The `getFileNameWithParent` utility method now always uses / as
+  a file separator instead of the platform-specific one (e.g. \ on
+  Windows). This ensures that baselines don't vary their error
+  messages (where this utility method is typically used) based on
+  which OS they were generated on.
+
 **8.2**
 
 * For unit tests, you can now specify the language level to be used

docs/api-guide/changes.md.html

@@ -29,6 +29,7 @@
 This is a \`code symbol\`    | This is a `code symbol`
 This is `*italics*`          | This is *italics*
 This is `**bold**`           | This is **bold**
+This is `~~strikethrough~~`  | This is ~~strikethrough~~
 http://, https://            | [](http://), [](https://)
 `\*not italics*`             | `\*not italics*`
 \`\`\`language\n text\n\`\`\`| (preformatted text block)

docs/api-guide/messages.md.html

@@ -52,7 +52,7 @@
 ### lintPublish Configuration
 
 The Android Gradle library plugin provides some special configurations,
-`lintConfig` and `lintPublish`.
+`lintChecks` and `lintPublish`.
 
 The `lintPublish` configuration lets you reference another project, and
 it will take that project's output jar and package it as a `lint.jar`
@@ -94,7 +94,7 @@
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 apply plugin: 'com.android.application'
 dependencies {
-    lintConfig project(':checks')
+    lintChecks project(':checks')
     // other dependencies
 }
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/api-guide/publishing.md.html

@@ -76,7 +76,7 @@
   will be checked during release builds (even if the lint target is not
   included).
 
-  Example: `fatal 'NewApi', 'InlineApi'`
+  Example: `fatal 'NewApi', 'InlinedApi'`
 
 `error` issue-list
 : Sets the severity of the given issues to error.

docs/book.html

@@ -4,6 +4,65 @@
 For information about internal improvements and API changes affecting
 lint check authors, see the API Guide.
 
+**8.4**
+
+* New built-in lint-checks:
+
+  Issue ID                          | Summary
+  ----------------------------------|-----------------------------------
+  `BuildListAdds`                   | Missing `add` call in `buildList`
+  `PublicKeyCredential`             | Creating public key credential
+  `SecretInSource`                  | Secret in source code
+  `LintBaselineFixed`               | Baseline issues fixed
+
+* The `LintBaseline` issue was reporting two different types of issues:
+
+  1. An informational message that a baseline was applied, listing the
+  number of errors and warnings that were filtered out because of the
+  baseline
+
+  2. Whether one or more problems listed in the baseline are no longer
+  reported, meaning the issue has likely been fixed -- so the baseline
+  can be updated (for example to prevent the issue from silently
+  reoccurring).
+
+  Since these are separate problems and you may want to configure one
+  and not the other to be a warning or an error, the `LintBaseline`
+  issue id is now only used for the first type of issue, and the second
+  one is reported under a new issue ID, `LintBaselineFixed`. If you had
+  previously suppressed `LintBaseline` in order to remove both of these
+  reports, you'l need to also suppress `LintBaselineFixed`.
+
+**8.3**
+
+* New built-in lint-checks:
+
+  Issue ID                         | Summary
+  ---------------------------------|-----------------------------------
+  `ActivityIconColor`              | Ongoing activity icon is not white
+  `SelectedPhotoAccess`            | Behavior change when requesting photo library access
+  `UseSdkSuppress`                 | Using `@SdkSuppress` instead of `@RequiresApi`
+  `WrongCommentType`               | Wrong Comment Type
+
+**8.2**
+
+* New built-in lint-checks:
+
+  Issue ID                             | Summary
+  -------------------------------------|-----------------------------------
+  `ForegroundServicePermission`        | Missing permissions required by foregroundServiceType
+  `ForegroundServiceType`              | Missing `foregroundServiceType` attribute in manifest
+  `IntentWithNullActionLaunch`         | Unsafe intent launched with no action set
+  `MutableImplicitPendingIntent`       | Mutable Implicit PendingIntent is disallowed
+  `PlaySdkIndexGenericIssues`          | Library has issues in SDK Index
+  `StartActivityAndCollapseDeprecated` | TileService.startActivityAndCollapse(Intent) is deprecated
+  `TilePreviewImageFormat`             | Tile preview is not compliant with standards
+  `WearBackNavigation`                 | Wear: Disabling Back navigation
+  `WearMaterialTheme`                  | Using not non-Wear `MaterialTheme` in a Wear OS project
+  `WearPasswordInput`                  | Wear: Using password input
+  `WearRecents`                        | Wear OS: Recents and app resume
+  `WearSplashScreen`                   | Wear: Use `SplashScreen` library
+
 **8.1**
 
 * Lint now supports and includes checks for Gradle version catalog
@@ -16,12 +75,14 @@
   ----------------------------------|-----------------------------------
   `NoOp`                            | Finds leftover code constructs which have no side effect or purpose
   `UnspecifiedRegisterReceiverFlag` | Missing `registerReceiver()` exported flag
+  `UnsafeIntentLaunch`              | Launched unsafe Intent
   `UnsafeImplicitIntentLaunch`      | Implicit intent matches an internal non-exported component
-  `ShortcutUsageDetector`           | Shortcut usage should be reported
+  `ReportShortcutUsage`             | Shortcut usage should be reported
   `UseTomlInstead`                  | Mixing and matching Gradle build file and TOML dependencies
   `KaptUsageInsteadOfKsp`           | Using kapt where KSP would also be available
   `BomWithoutPlatform`              | BOM artifact added as a dependency instead of as a platform
   `ProviderReadPermissionOnly`      | Provider with readPermission only and implemented write APIs
+  `MutableImplicitPendingIntent`    | Mutable implicit PendingIntent is disallowed
 
   (The `NoOp` and `UnsafeImplicitIntentLaunch` lint checks are
   currently disabled by default.)

docs/index.html

@@ -113,6 +113,16 @@
   `bytecode` test file, lint can generate the .class file binary
   content automatically if it is pointed to the `javac` compiler.
 
+`LINT_TEST_KOTLINC_NATIVE`
+: When writing a lint check unit test, when creating a `klib` file,
+  lint can generate the `.klib` file binary content automatically
+  if it is pointed to `kotlinc-native`.
+
+`LINT_TEST_INTEROP`
+: When writing a lint check unit test, when creating a `c` or `def`
+  test file, lint can generate the `.klib` file binary content
+  automatically if it is pointed to `cinterop`.
+
 `INCLUDE_EXPENSIVE_LINT_TESTS`
 : When working on lint itself, set this environment variable to `true`
   some really, really expensive tests that we don't want run on the CI
@@ -134,6 +144,19 @@
   shortcut for invoking the `lintFix` targets or running the `lint`
   command with `--apply-suggestions`.
 
+`lint.autofix.imports`
+: If `lint.autofix` is on, setting this flag will also include updating
+  imports and applying reference shortening for updated code. This
+  is normally only done in the IDE, relying on the safe refactoring
+  machinery there. Lint's implementation isn't accurate in all cases
+  (for example, it may apply reference shortening in comments), but
+  can be enabled when useful (such as large bulk operations along with
+  manual verification.)
+
+: Turns on auto-fixing (applying safe quickfixes) by default. This is a
+  shortcut for invoking the `lintFix` targets or running the `lint`
+  command with `--apply-suggestions`.
+
 `lint.html.prefs`
 : This property allows you to customize lint's HTML reports. It
   consists of a comma separated list of property assignments, e.g.