Document the String API workflow with compiler plugin
@koperagen is already working on this.
Since Feb 9, 2026.
- Dominant language
- Kotlin
- Stars
- 1.1k
- Forks
- 83
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 30
Description
Simply put, code similar to this should compile: rawDf.select { “str”<Int>() }.str. I.e. after a column is references by a String API, it's implied such column should exist => plugin updates the schema accordingly.
Goal here is to provide workflow alternative to defining full @DataSchema for AnyFrame. Instead, sometimes information from a few "String API" calls can be enough to migrate to typesafe API. It enables "incremental migration".
Related change in the library:
https://github.com/Kotlin/dataframe/pull/1666, https://github.com/Kotlin/dataframe/pull/1659, https://github.com/Kotlin/dataframe/pull/1667
It all needs to be documented with its own page: an example of a moderately sized pipeline, few shorter examples with CS DSL operators that are recommended to use
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.