Support K2 about compose-destinations HOT 7 OPEN

You scared me for a moment.. I thought for a moment that they would be dropping that completely 😅 made no sense but we never know..

I should have made it clearer. That is only for testing KSP2 compatibility with 1.0.20 FooIbar@d7e79dd.

Update: Tested with 1.0.21, it's only partially fixed. Filed a bug on KSP google/ksp#1910.

from compose-destinations.

Looks like K2 is enabled by default in Kotlin 2.0. Did anyone get the library working with k2 enabled?

from compose-destinations.

You can use it with K2, we've been doing that for a while, just don't use KSP2.

from compose-destinations.

Looks like FooIbar@7875839 is the only change needed to support KSP2.
Note KSP 1.0.20 does not have google/ksp#1871, so those arguments that have class literals as default values need to be explicitly specified, e.g.

@Destination<RootGraph>(navArgs = Nothing::class, style = DestinationStyle.Default::class)

from compose-destinations.

Ok thank you @FooIbar

But just so we're clear. Using 1.0.20 KSP means we'd have to specify all field defaults for annotations that have class types, but only if using K2 as well, right?

from compose-destinations.

Ok thank you @FooIbar

But just so we're clear. Using 1.0.20 KSP means we'd have to specify all field defaults for annotations that have class types, but only if using K2 as well, right?

Yes, only if using KSP2.
That fix has been cherry-picked to the 1.0.21 branch google/ksp@fc0cdbf, which should be released soon?

from compose-destinations.

You scared me for a moment.. I thought for a moment that they would be dropping that completely 😅 made no sense but we never know..

from compose-destinations.