Skip to content

A few more docs updates #103

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 16, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion docs/api-guide/changes.md.html
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,13 @@
information about user visible changes to lint, see the User
Guide.

**8.9**

* Lint's testing infrastructure support for testing quickfixes
(`expectFixDiffs()`) now also validates that the modified
source file is valid Kotlin, Java or XML. You can control
this using the `lint().verifyFixedFileSyntax()` option.

**8.8**

* For the string-replacement quickfix, you can now specify
Expand Down Expand Up @@ -371,7 +378,7 @@
Previously only `visitMethodCall()` was triggered.

* Quickfixes can now create and delete new files; see
`LintFix#newFile` and `LintFix#deleteFile`..
`LintFix#newFile` and `LintFix#deleteFile`.

* For quickfixes, the `independent` property had inverted logic;
this has now been reversed to follow the meaning of the name.
Expand Down
11 changes: 11 additions & 0 deletions docs/api-guide/quickfixes.md.html
Original file line number Diff line number Diff line change
Expand Up @@ -297,6 +297,17 @@
)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

## Verifying Quickfixes

Lint's test support will also attempt to verify that your quickfixes
still produces a valid Kotlin, Java or XML source file. It does this
by parsing these files after testing the quickfixes using
`expectFixDiffs()`. It will only complain if the fixed source file didn't
already have parsing errors *before* applying the fix.

You can control this behavior using the `.verifyFixedFileSyntax()` method
on the `lint()` task.

## Emitting quick fix XML to apply on CI

Note that the `lint` has an option (`--describe-suggestions`) to emit
Expand Down
11 changes: 11 additions & 0 deletions docs/usage/changes.md.html
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,16 @@
For information about internal improvements and API changes affecting
lint check authors, see the API Guide.

**8.10**

* New built-in lint checks:

Issue ID | Summary
----------------------------|-------------------------------------------
`Aligned16KB` | Native library dependency not 16 KB aligned
`TrimLambda` | Unnecessary lambda with `trim()`
`UnnecessaryArrayInit` | Unnecessary array initialization

**8.9**

* New built-in lint checks:
Expand All @@ -14,6 +24,7 @@
`PrivacySandboxBlockedCall` | Call is blocked in the Privacy Sandbox
`UseRequiresApi` | Use `@RequiresApi` instead of `@TargetApi`
`WrongSdkInt` | Mismatched SDK_INT or SDK_INT_FULL
`UseKtx` | Use KTX extension function

* The `ImplicitSamInstance` check is now turned on by default, and covers
a broader set of scenarios.
Expand Down
Loading