Albert Chang
Albert Chang
Actaully I've thought of that but the problem is that in order to use `Showkase.getBrowserIntent(context)` we need `com.airbnb.android:showkase`. If we go this way, we have to put that in debug...
@vinaygaba Do you mean you are putting all the preview functions in debug source set? That's a lot of setup and prevents preview of private functions so we definitely won't...
@vinaygaba > Maybe R8 is still intelligent enough to strip them off Yes, definitely intelligent enough. That's one of the reasons why R8 exists. > Showkase does have first class...
OK, it's your library after all but it would be kind of you if you could tell me where you are using ui-tooling as I've searched through the code before...
But that's `showkase-processor`, isn't it? Unlike `showkase` and `showkase-annotation`, `showkase-processor` isn't a `implementation` dependency (it's a `ksp`/`kapt` one instead) and will not be in the runtime classpath so its dependencies...
It seems that `showkase-processor` is a java module thus can't depend on any Android (aar) libraries including `ui-tooling-preview`. However the current way of specifying the fully-qualified name of `Preview` class...
To be clear, by Kotlin Multiplatform support do you mean support for Compose Multiplatform or some UI framework independent solution (which will be much more complicated I think)? Also what...
I rewrote this plugin and removed all the usages of deprecated APIs (and also migrated to the new AGP variant API). It's working well with AGP 8.0.1 / Gradle 8.1.1...
This bug is consistently reproducible when using AndroidX Fragment 1.5.0 and above. You can reproduce it by simply adding `implementation "androidx.fragment:fragment:1.5.5"` to FishBunDemo/build.gradle.