A modern programming language that makes developers happier.

kotlinlang

Hello everyone, here is the KSP <https://android-developers.googleblog.com/2021/09/accelerated-kotlin-build-times-with.html|1.0.0 stable release>! We want to thank you for being KSP's early adopters and giving us so many invaluable feedback / contributions. With all your help we finally are able to make the first stable release of KSP.

The next steps of KSP will be supporting new Kotlin compiler, better multiplatform support, performance and bug fixing. We'd also like to spend more time working with you to bring KSP to everyone. Of course, please feel free to let us know if you have any ideas on what can be done next.

Again, please give it a try and let us know what you think!

P.S. The version convention is unchanged; The exact version number is 1.5.30-1.0.0 to match the compiler version.

thanks for catching this, will update the document :slightly_smiling_face:

In the blog post in the “How to get started” section there is a link to  <https://github.com/google/ksp/releases/download/1.5.30-1.0.0/artifacts.zip|KSP playground project>, which points to released binary *ksp* artifacts. Is it right? Probably what was meant, ist <https://github.com/google/ksp/releases/download/1.5.30-1.0.0/playground.zip|Playground project>  as mentioned in <https://github.com/google/ksp/blob/main/docs/quickstart.md|Quickstart documentation>

Also sample playground project misses entry for generated code folders, which makes Intelij redish
```sourceSets.main {
    kotlin.srcDir("build/generated/ksp/main/kotlin")
}```
Otherwise :+1:, I like the playground project highlighting various use cases, even Java code generation

that link to the artifacts is probably a mistake on our side, you should refer to the playground linked in the quckstart doc. As for the generated config, it is intended as adding it to build script is a temporary workaround and we intend to address this in a more elegant way in the future