Hey! Is there a reason kotest-property <exposes sh...
# kotest
b
Hey! Is there a reason kotest-property exposes shared assertions (and kotest-common) as API, instead of having them as implementation dependencies?
I use the property testing library but with another assertions library, and contributors accidentally using similar assertions exposed by kotest instead doesn't seem ideal for consistency
e
@sam do you know?
s
Probably could be implementation if no other side effects. It may have been set to api back when this stuff was fairly new and buggy in gradle.