Ivan “CLOVIS” Canet

icon indicating a website link https://ivan.canet.dev icon indicating an email [email protected]

icon company @4sh icon location Bordeaux, France icon location Software development & architecture, specialized in Kotlin & Rust

Results 199 comments of Ivan “CLOVIS” Canet

Compilation error when applying the plugin

Version of what? The Kotest plugin version is 5.9.1, as written in the issue.

Dokka 2+: Creating a custom format requires access to an internal configuration

`DokkaFormatPlugin` doesn't seem to have a `configure` method that I can override? I'm a bit confused

Dokka 2+: Creating a custom format requires access to an internal configuration

Weird. Just IDEA that says there is no method to override. I tried to copy-paste your snippet in [this file](https://gitlab.com/opensavvy/automation/dokka-material-mkdocs/-/blob/main/dokka-mkdocs/src/main/kotlin/DokkaMkDocsPlugin.kt?ref_type=heads#L13), I don't know where else it could be?

Dokka 2+: Creating a custom format requires access to an internal configuration

uh, I'm dumb. Thanks, I'll try it again then :|

add distant horizons support

Please :pray:

Nested multimodule tasks are broken in Gradle 8

Same error for me, reproducible in GitLab CI: [job](https://gitlab.com/opensavvy/decouple/-/jobs/4010536009) | [code](https://gitlab.com/opensavvy/decouple/-/commit/f7dcdaf7aa2e6fa6e78d077a2cbab1d69bccb6ba). Reproduced with Gradle 8.0.2, Dokka 1.7.20 and 1.8.10.

Nested multimodule tasks are broken in Gradle 8

After migrating to Gradle 8.1.1 and Dokka 1.8.20, without using any of the mentioned workarounds, I do not have this problem anymore.

Nested multimodule tasks are broken in Gradle 8

Nevermind, it seems to depend on the project. I have another project using Gradle 8.1.1 and Dokka 1.8.20, in which the workaround is still necessary.

Introduce Flow.all/any/none operators

Simplified implementation: ```kotlin suspend fun Flow.any(predicate: (T) -> Boolean) = this .filter { predicate(it) } .map { true } .onEmpty { emit(false) } .first() ```

Consider deprecation cycle for `CoroutineDispatcher.invoke`

For context, it was originally added in #428 as an experiment. As far as I know, it is very rarely used (if at all) in the ecosystem.