You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would let us use the plugins block in our unit tests instead of using the buildScript and then the apply.
This will also allow us to unit test with the Gradle Kotlin DSL. The ktlint accessors would automatically get generated by gradle and we could make sure that the API was what we wanted in our unit tests.
The text was updated successfully, but these errors were encountered:
We could significantly simplifies the tests by using the GradleRunner.withPluginClassPath() API as proposed in this github issue comment:
gradle/kotlin-dsl-samples#1178 (comment)
It would let us use the
plugins
block in our unit tests instead of using thebuildScript
and then theapply
.This will also allow us to unit test with the Gradle Kotlin DSL. The
ktlint
accessors would automatically get generated by gradle and we could make sure that the API was what we wanted in our unit tests.The text was updated successfully, but these errors were encountered: