Mocks incompatible with value classes about mokkery HOT 3 CLOSED

I was able to reproduce it. It affects JVM and Wasm. Fixing it for JVM should not be a big problem, but it might be problematic for Wasm. Anyway, I will do my best to provide a fix.

from mokkery.

Fixed in Mokkery 1.6.1. Thank you for reporting the issue!

• For JVM all value classes should work properly now.
• For Wasm it fixes only standard library value classes (Result, Duration). Other value classes have to be registered with:

AutofillProvider.forInternals.types.register { ValueClass(null) }

• Other targets were not affected.

from mokkery.

Thank you! At the moment, fixing the JVM compatibility is the only thing I need (atm, haha). The library looks nice, but the lack of this feature prevents me from adopting it.

from mokkery.