eygraber
06/13/2022, 1:51 AMorg.jetbrains.compose
plugin and the Jetbrains compose artifacts (which should redirect to the Google artifacts).
I started writing some tests for it, but the compose artifacts aren't visible in the test code. For example, if I have implementation(compose.material)
, android.compose.material.Text
doesn't resolve in a test file in the IDE, even though it runs fine. Adding testImplementation(compose.material)
doesn't work either. I have to explicitly depend on the Google artifacts in order for the IDE to resolve the type.
I'm using Electric Eel latest alpha.Big Chungus
06/13/2022, 9:47 AMBig Chungus
06/13/2022, 9:48 AMeygraber
06/13/2022, 12:57 PMtestImplementation
includes all dependencies from implementation
? So it shouldn't need to be api
.
In any case, the issue is that the types don't resolve even when there's an explicit testImplementation
dependency on the Jetbrains compose artifacts.
I'm assuming the issue is with the redirecting to the Google artifacts for test configurations, or an issue with Gradle metadata.Big Chungus
06/13/2022, 3:19 PMI thought that testImplementation includes all dependencies from implementation? So it shouldn't need to be api.That's true. I meant jb library itself does not expose androidx artefacts as transitive dependencies