Dale King

Seeing this as well, but on any of the 10.x versions. Luckily in my case what I needed to exclude was an entire sourceset so was able to just disable...

Thinking about it some more, the only part of this whole system that should care whether state is a built value is the reducer. I am starting to question why...

Any update on this? This keeps me from using the plugin.

That would be fine too. I am looking to use dependency injection to inject Clock instance into code and to be able to inject an instance that I can easily...

I view version 2 as a HUGE downgrade. The ability to use callable references was a huge advantage of Mockative. They allowed you to set up the behavior for a...

Did some playing around with implementing this without ksp and here is code to handle functions with functions with 0 or 1 parameter in suspend and non-suspend varieties. Note that...

Revisiting this and here is what I came up with: ``` @file:Suppress("UNUSED_PARAMETER") import io.mockative.Invocation.Function import io.mockative.Mockable import kotlin.jvm.JvmName import kotlin.reflect.KClass class FunctionMock(private val returnsUnit: Boolean) : Mockable(stubsUnitByDefault = false), ()...

Since Mockative 2 is a major downgrade in functionality, it doesn't really help

I am very much against the idea of adding TimeZone into the Clock interface. One of the best parts of kotlinx-datetime is the way that there is a stark separation...

Did some refactoring and renaming: ``` interface DateTimeSource : Clock, TimeSource { val timeZone: () -> TimeZone val localDateTime get() = toLocalDateTime(now()) val localDate get() = localDateTime.date val localTime get()...