Dan Cîmpianu
Dan Cîmpianu
I've also encountered this issue, but decided not to use mocks, as the static nature of the library makes it expensive and cumbersome to use something like MockK's `mockkObject()`. Instead,...
Yes, this seems to be a problem in the way the API handles base currencies. See also #34 and #70. As a workaround I would suggest not querying for base...
@OliverO2 I think you have accidentally mixed up `finalizeSpec` with `afterSpec`. That one, indeed, should run once per spec instance, of which there are 2, respectively 3 depending on isolation...
@sksamuel I think the confusing part is this bit of the documentation _(regarding `finalizeSpec`)_: > Regardless of how many times the spec is instantiated, for example, if InstancePerTest or InstancePerLeaf...
@sksamuel I think I finally understand the underlying issue here. I will try to summarize the facts in hopes of clearing up the confusion in this thread. Let's take the...
> This will be merged in as soon as we release 5.8.1 @sksamuel Any updates on the 5.8.1 release? Is there something blocking it or are you just waiting for...
Small tip for the workaround in the meantime: you can use `runtimeOnly(compose.material)` instead of `implementation` in order to not pollute the imports with non-material3 composables.
Duplicate of #95. Since you provide the external dependency in the Koin DSL, which is runtime, the compiler check cannot verify it at build time, hence the error.
Yes, the current implementation is unfortunately, global. See #92 and #102.
This problem is similar to what I described in #95. Unfortunately the checks don't play nice when combining annotated modules and manual DSL. Since you register the Android context in...