Zac Sweers
Zac Sweers
That way we could have a `ciGlobalCheckSortDependencies` that is skippy-compatible
Then we can run something like ciGlobalSpotlessCheck and have it only run on affected projects
Currently we have two different implementations for computing dependencies. 1. Module stats computes shallow dependencies from explicit build file declarations. 2. Skippy uses `SerializableDependencyGraph`, which uses a subset of configurations...
This allows them to be generated in one machine and usable in another
This implements a new `Settings` plugin in Gradle for global configuration of different sorts. Highlights - Auto-configure AGP 8.x's new `Settings` plugin with values for `minSdk` and `compileSdk` + expose...
Would be an either-or with the regular detekt plugin https://github.com/detekt/detekt-compiler-plugin Unclear how baseline generation works
A gradle property with a comma-separated list of library aliases that should be added to detekt rulesets when detekt's gradle plugin is applied. This would allow us to more readily...
Saw this the android keynote from IO. We scrape some xml file manually in the sample right now
Resolves #88 by adding test coverage for it too
https://android-developers.googleblog.com/2023/12/ksp2-preview-kotlin-k2-standalone.html