Hey, is this possible to launch the generation only for Unit Testing such as testImplementation() or...

# ksp

[atlantis210]

Hey, is this possible to launch the generation only for Unit Testing such as testImplementation() or kspTest() ?

[mbonnin]

https://kotlinlang.org/docs/ksp-multiplatform.html#avoid-the-ksp-configuration-on-ksp-1-0-1

Try allowAllTargetConfiguration=false and kspTest ?

[mbonnin]

Looks like it's more

ksp.allow.all.target.configuration=false

in your gradle.properties

[atlantis210]

looks like it's already false as I'm on ksp2 but I'll try the kspTest

[atlantis210]

Thanks I managed what I wanted to do but I have another question following. I will post it on the main thread

[atlantis210]

Can we force the lib to be solely for tests and usable only with kspTest() ?

[mbonnin]

Can you elaborate? What lib?

[atlantis210]

Sorry I was thinking about my KSP lib. Is it possible to force it to be only usable with kspTest when adding it in the app ?

[mbonnin]

There's no really such thing as a KSP lib. There's a processor and generated code

[mbonnin]

If you want the generated code to be only usable from test then you should add your processor to the kspTest configuration

[atlantis210]

yeah OK. So if someone wants to use it on prod code there is no way to restrict it, right ?

[atlantis210]

What I meant was if I was to put my processor on a public github repository, there is no way of restricting it to using it only on tests. But I think I have the answer, thanks for everything

[mbonnin]

Oh yea, your processor knows nothing about what source set it is used with