Do not support KSP2.

[li-fcb1899]

Kotlin: 2.2.20
Gradle: 9.0.0
Dataframe: 1.0.0-dev-8421

When I build up my gradle, it reports error:

org.gradle.api.internal.tasks.DefaultTaskContainer$TaskCreationException: Could not create task ':kspKotlin'.
Caused by: java.lang.IllegalStateException: Detected KSP2. This is not supported by the DataFrame Gradle/Ksp plugin. Add 'ksp.useKSP2=false' to 'gradle.properties'.

So, I add 'ksp.useKSP2=false' to 'gradle.properties'.
But today, it warning:

We noticed you are using KSP1 which is deprecated and support for it will be removed soon - please migrate to KSP2 as soon as possible. KSP1 will no longer be compatible with Android Gradle Plugin 9.0.0 (and above) and Kotlin 2.3.0 (and above)

[koperagen]

Hi
We have a blocking issue on KSP side that prevents our processor from working in KSP2:
google/ksp#2524

KSP processor has 2 features now: @DataSchema and @ImportDataSchema. For @DataSchema you can try our new compiler plugin:
https://kotlin.github.io/dataframe/compiler-plugin.html#setup
It's even much more powerful: it evaluates expressions and reflects a lot of schema changes made by operations in types.

As for @ImportDataSchema, we're working on it. If you have generated schemas, you can copy-paste them into the project files from build/generated as a migration path. We have API to generate new schemas as well: https://kotlin.github.io/dataframe/dataschemagenerationmethods.html

[li-fcb1899]

Hi We have a blocking issue on KSP side that prevents our processor from working in KSP2: google/ksp#2524

KSP processor has 2 features now: @DataSchema and @ImportDataSchema. For @DataSchema you can try our new compiler plugin: https://kotlin.github.io/dataframe/compiler-plugin.html#setup It's even much more powerful: it evaluates expressions and reflects a lot of schema changes made by operations in types.

As for @ImportDataSchema, we're working on it. If you have generated schemas, you can copy-paste them into the project files from build/generated as a migration path. We have API to generate new schemas as well: https://kotlin.github.io/dataframe/dataschemagenerationmethods.html

When I replace the plugin, it works.

But I meets a new error.

Why "this" can only be used once in the run scope?
Need take the second "this[]" replace with "get()" to resolve error.

[koperagen]

What happens if you change get => this[] again? I tried to reproduce, but don't see the same errors. Maybe it's related to
fun main() = ? fun main(): Unit = maybe will work better?

[li-fcb1899]

What happens if you change get => this[] again? I tried to reproduce, but don't see the same errors. Maybe it's related to fun main() = ? fun main(): Unit = maybe will work better?

Type of the first "this" is Dataframe<Any_71>.

But type of the second "this" is Scope0.

[li-fcb1899]

What happens if you change get => this[] again? I tried to reproduce, but don't see the same errors. Maybe it's related to fun main() = ? fun main(): Unit = maybe will work better?

fun main(): Unit = and fun main() {} both can't resolve this error.

[koperagen]

But type of the second "this" is Scope0.

Got it. It's expected side effect of plugin generating extension properties for type safe data access, although in combination with String API and without initial data schema for now it cannot infer much information about column structure.
To give an example what it can do:

val df = dataFrameOf("col" to columnOf("42"))
val col: DataColumn<Int> df.convert { col }.with { it.toInt() }.col

As for the original problem, cannot suggest anything except your existing workaround. I'll see if some sort of compiler warning can be added for such references, so thank you for letting me know about this problem!

[zaleslaw]

TODO: Need to be documented better

[zaleslaw]

@koperagen could you please verify that we are properly reflecting this in documentation on site